-
-
Notifications
You must be signed in to change notification settings - Fork 470
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
Use of state parameter in authorisation code flow #190
Comments
The state parameter is just stored and echoed back to the client. Is there something other than that you are referring to? |
Thanks for your reply. So, there is no change in the following code piece? If the user’s request has state, it is just echoed back? Nothing to add on the implementor’s side?
|
I pass in a state, but it does not appear to be echo's back to client on the final redirect. I am using angular as the front end user allow/deny page, but this is redirected after the initial authorisation call has been made, so the state should be in the session right? |
I have the same problem. Anybody knows how to handle a state URL parameter to echo back on the final redirect? |
Still having this problem as well (on final redirect), any solutions? |
Still having this problem as well, any solutions? UPDATE: |
It seems like the state parameter is supported in the implementation, but not sure how it is used in the AS side. Could you give an example when granting code, how the server can callback also the state value?
The text was updated successfully, but these errors were encountered: