-
Notifications
You must be signed in to change notification settings - Fork 368
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
Set expires at for password credentials flow #210
Conversation
Signed-off-by: Beorn Facchini <[email protected]>
Thank you! Would you mind adding a (failing) test case for this too? |
Added a failing check to the final test case. |
perfect, thank you! |
Hmm, I just upgraded our fosite dependency and this PR seems to have broken my app's use of fosite. The expiration time set in the session, which seems like it should be preferential, is now overridden by this value. Previously, the behavior used the expiration times in the session set here: Lines 46 to 69 in dd9398e
I can work around this be setting the configuration variable to the access token time that we want, but that seems to defeat the purpose of the custom expiration times in the session. |
Unless I was perhaps misusing the |
This might be #211 |
In the case of pre-filling the session expiration time it might help to wrap all session expiration time setters with a nil check: |
Signed-off-by: Beorn Facchini <[email protected]>
Noticed that expires at is not set in the session by default unlike the authorize code, client credential and refresh flows.