-
Notifications
You must be signed in to change notification settings - Fork 43
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
Fix management of tokens lifetime following RFC9068 #620
Conversation
Kudos, SonarCloud Quality Gate passed! |
.../iam/apps/dashboard-app/components/clients/client/tokensettings/tokensettings.component.html
Outdated
Show resolved
Hide resolved
.../iam/apps/dashboard-app/components/clients/client/tokensettings/tokensettings.component.html
Outdated
Show resolved
Hide resolved
Follow the RFC https://datatracker.ietf.org/doc/html/rfc9068 |
When AT does not expire, the |
@federicaagostini probably a new issue related to "exp" claim could be a good idea |
0d5c7c7
to
b972ac9
Compare
f13d835
to
5d77475
Compare
when a client request trough API does not explicit one
since the "Token" tab with token-related settings is visible only by Admins. When the lifetimes are not requested during a client update/save, set them to the default values (that are deployment options).
Kudos, SonarCloud Quality Gate passed! |
Please retry analysis of this Pull-Request directly on SonarCloud. |
This reverts commit 3749a72.
The Access Token and Refresh Token lifetimes are configurable by admins via web interface. #545
The exp claim will always appear into access tokens (following RFC9068). #648