Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Machine identity secrets disappear before graceperiod of TTL has expired #2902

Open
Metachemix1 opened this issue Dec 20, 2024 · 1 comment

Comments

@Metachemix1
Copy link

Describe the bug

After creating a machine identity and client key/secret combination to use in a Gitlab pipeline, the client secret disappears within the next 24 hours.

Client secret was created with
TTL: 0 (to keep it forever, for development purposes)
Max number of uses: 0 (I assume, to disable the amount)

Also tested with
TTL: 1209600 ( 2 weeks in seconds format)

After a few successful tests on the same day, the next day the same tests failed due to invalid credentials. Further investigation showed that the secret disappeared again.

To Reproduce

Steps to reproduce the behavior:

  1. Go to Access Control on Infisical WebUI
  2. Go to Machine identities
  3. Click on Create identity in order to create a new machine identity
  4. Fill in a name and assign a role: member
  5. Click the + button to add a project with secrets assigned to it
  6. Click Create Client Secret in order to create a new Client secret
  7. Fill in the description
  8. Set the TTL to 0 in order to disable the expiry
  9. Set the Max Number of Uses to 0 in order to allow infinite usage.
  10. Check the next day if the secret still exists or disappeared

Expected behavior

Client secret is successfully created
TTL and max usage properties are respected and the secret stays after 24 hours

Actual behavior

Client secret is successfully created
TTL and max usage are not respected, secret disappears within 24 hours, might be cleaned up through cleanup cronjob because it somehow got expired.

Platform you are having the issue on:

Version: v0.82.0-postgres

Additional context

#2393 seems to have the same issue, but got closed due to not reproducible after updating

I've joined the slack community and posted a question in the #infisical-help channel where a similar issue was mentioned earlier, without a solution.

https://infisical-users.slack.com/archives/C04BSBMQAQ7/p1734413432450629

@akhilmhdh
Copy link
Member

Please use. a version v0.82.1 or higher. This has been fixed and was an issue on image v0.82

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants