Increase token lifespans in the default realm created by DevServices for Keycloak #28175
Conversation
This file contains 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
gsmet
approved these changes
Sep 25, 2022
sberyozkin
deleted the
devservices_for_keycloak_increase_token_lifespan
branch
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.
Dev Services for Keycloakwill create a default realm if no custom realm has been provided, and after a login to this realm, Keycloak will issue short-lived access and id tokens, which is inconvenient when using them from Dev UI - for example, I tried Dev UI, then started looking at the tests (another time I was examining the tokens and was using them slowly enough in UI), and then retrying the token from Dev Ui fails with401.So I've increased it
600to secs (10 mins), users can then change it further if needed via aKeycloak Adminlink, 10 mins seems to be just enough, but we can tune further