feat: Add ability to temporary update expiry times through API #4050
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
Signed-off-by: Alby Hernández <donfumero@gmail.com>
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.
Overview
I am adding ability to change default expiry times through the GRPC API. Thos changes are not persisted as the intention is to use this only when needed for some tokens by admins/operators
What this PR does / why we need it
This PR is needed for those deployments that need to generate long-lived tokens for special use cases such as QA flows, that are not able to generate tokens on their own from time to time. This allos operators to generate one token with a long expiry time for them.
It closes #4045
Special notes for your reviewer
n/a