-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Is it possible to add a callback after the sendAccessTokenResponse method of accessTokenResponseHandler? #1148
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
Comments
@jacko9et I'm not understanding your question.
This is referring to the token endpoint.
And this is referring to the authorization endpoint. Can you provide more details and please be specific on exactly what you are trying to implement. Thanks. |
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed. |
He want the user to re-authenticate every time they are redirected to the OAuth server. |
@ramonmalcolm10 What you described does not sound like what @jacko9et is asking. Your description sounds very much like gh-501. I will wait for @jacko9et to respond. |
Sorry for the late reply. Because the session is needed to store the state in the process, I think the session needs to be cleaned up after the client obtains the token. The default accessTokenResponseHandler cannot be extended using a delegate class without changing the default behavior. I don't think it's a problem to close the modification, but the extension cannot reuse the code because of insufficient scalability. It is proposed to add a callback method after accessTokenResponseHandler to provide sufficient scalability. |
@jacko9et Thanks for the explanation.
The OpenID Connect 1.0 parameter
|
Is it possible to add a callback after the sendAccessTokenResponse method of accessTokenResponseHandler?
I don't want to change the default behavior, I just want to clean up the session after the response is successful, so that every time the /oauth2/authorize endpoint is triggered, it will re-login.
The text was updated successfully, but these errors were encountered: