-
Notifications
You must be signed in to change notification settings - Fork 21
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
TTL is not being respected in V1.3 #159
Labels
bug
Something isn't working
Comments
@georgeskill Thanks for the bug report. I've added this to our sprint. |
@georgeskill FYI, if you can run your Vault server with log at DEBUG level, you will see logs showing which TTL is used:
|
@alexhung Thanks for the prompt response. Here are the logs when running these commands:
|
alexhung
added a commit
that referenced
this issue
Mar 11, 2024
Fix user token config fall back logic
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The default TTL for tokens is not being applied to user tokens in V1.3. V1.2 applied the correct default TTL to user tokens, but V1.3 has broken my org's TTL policy.
To Reproduce
When using the V1.3 plugin, I run these commands:
vault secrets enable -path=artifactory artifactory_1.3
vault write artifactory/config/admin url=<artifactory_instanceurl.com> access_token=<token>
vault write artifactory/config/user_token scope="applied-permissions/user" default_ttl=24h max_ttl=48h default_description="Generated by Vault"
vault read artifactory/user_token/<username>
This is the output of the previous command:
The lease duration is not connected to the default_ttl. Whereas, when I run the exact same commands with version 1.2 of the plugin, my user token's TTL is correct.
Here is my vault config:
I am interacting with an Artifactory instance that is running version EnterpriseX 7.77.5
Requirements for and issue
curl
it at$host/artifactory/api/system/version
Expected behavior
The default TTL should be honored for user tokens with V1.3
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: