Skip to content

Conversation

@ToniIltanen
Copy link
Contributor

modified access token query to support client_secret_post based token query

client_id and client_secret added to support client_secret_post based auth on token request
id_token and scope are not valid variables in access token query.
(https://connect2id.com/learn/openid-connect codeflow step2)
Copy link
Contributor

@triplem triplem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The account_controller_patch.rb should have been modified as well, to avoid the usage of the used user_name. I have already adopted it. See #4.

query = {
'grant_type' => 'authorization_code',
'code' => code,
'scope' => 'openid profile email user_name',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On https://nat.sakimura.org/2012/01/26/scopes-and-claims-in-openid-connect/ the following can be found:

profile – OPTIONAL. This requests that access to the End-User’s profile Claims excluding the address and email Claims at the UserInfo Endpoint be granted by the issued Access Token.
email – OPTIONAL. This requests that access to the email and verified Claims at the UserInfo Endpoint be granted by the issued Access Token.

I guess, removing all of the above in the scope does not really makes sense, does it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants