-
Notifications
You must be signed in to change notification settings - Fork 189
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
Support for multiple response types #83
Comments
For implicit and hybrid flow, enabling "token" along with code/id_token would be much helpful |
Any Update. |
Hello, Is this request need any further reasons or inputs from my end ? |
Pinging here to enable this request open. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I'd like to reopen this topic. I'm looking to implement the hybrid flow ("code id_token") and that fails with the current version of the gem the |
Same problem over here. Our provider recommends the hybrid flow ("code id_token") in our situation. We cannot currently achieve this with this gem. Is there any solution for this or are there plans to implement this? |
I do not think anyone is working actively unless it is for their own usage. |
I guess this is what you are looking for? Maybe try it out, see if it works for you? |
Ah nice, missed that one. Good thing it is mentioned here now. Thanks! |
Currently, response_type can be either code or id_token.
Does this gem have support for multiple-valued response types, such as id_token token?
If so, what is the correct format for specifying them in the config? If not, can this functionality be added?
See the following for references:
https://openid.net/specs/openid-connect-core-1_0.html#Authentication
The text was updated successfully, but these errors were encountered: