scoped tokens: document 1-year max TTL - #73
Merged
Merged
Conversation
me.generateToken now accepts 60s–365 days (default still 15 minutes). Keep recommending short TTLs and service accounts for durable identities.
|
Preview deleted (PR closed). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Document that
me.generateToken/deploys me generate-tokennow accept a TTL of 60s–1 year (default still 15 minutes).Still recommend a short TTL for one-off tasks and a service account when the credential needs its own durable identity.
Ship with deploys-app/api#137 and https://github.com/deploys-app/apiserver/pull/255 so the published docs match the running clamp.
Test plan
content/access/scoped-tokens.mdfor leftover "1 hour" / "60–3600" claims.