-
Notifications
You must be signed in to change notification settings - Fork 435
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
Question about the validateState and checks for expiration #825
Comments
I consider disabling the id_token lifetime check per configuration. I have had this request quite often. Thanks for reporting Damien |
Also experiencing this. From what I can see, there's nothing in the RFC that indicates that the TTL of the id_token should be an indicator of how long the session of an external app should last. Therefore I consider this a bug, and that it shouldn't be solved by being able to config "away" the relevance of the id_token, as it's not really relevant in the first place. If you, for some reason, need to at all times have a valid id token, that should be an opt-in. |
we add support for this in V12 |
added in V12, default is with the id_token check, you can config this to stop the check.
Thanks for reporting |
We like to use the lifetime of our accessToken as leading to determine if we need to refresh them or not.
I have two questions:
We would like to be able to skip this check. And in addition to that we would like to be able to check of the accessToken is not expired. This also happens in the callback.services.ts:
const accessTokenHasExpired = this.authStateService.hasAccessTokenExpiredIfExpiryExists();
I hope you can help us with this or maybe we are lacking some knowledge about the importance of the identityToken lifetime, in that case, please help us with some explanation.
The text was updated successfully, but these errors were encountered: