use refreshable tokens for api auth #1044
Merged
+2
−2
Conversation
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
nemacysts
approved these changes
Apr 30, 2025
|
@piax93 just curious: can this be merged/released at any time or does this require doing any puppet/etc shenanigans in preparation? |
|
cc @Qmando since you might know the answer to that as well |
|
@nemacysts It can be released. The Puppet shenanigans were already done. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The new version adds an option to use an authentication flow with refresh tokens, which will allow
tronctlcommands to be run unattended for over the set duration of an identity token (which is fixed to 1 hour). Refresh tokens are valid for 90 days, which should be more than enough for all use cases.