Skip to content
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

Mentioning of PKCE related parameters #125

Open
janakamarasena opened this issue Nov 13, 2024 · 0 comments
Open

Mentioning of PKCE related parameters #125

janakamarasena opened this issue Nov 13, 2024 · 0 comments

Comments

@janakamarasena
Copy link

Under section 5.1. “Authorization Challenge Request” the spec lists the “code_challenge” and the "code_challenge_method" as optional parameters. As this protocol establishes direct communication between the client and the AS I don’t see a real requirement to mention PKCE related parameters here. Please let me know if I have missed anything here.

As I understood, using these two parameters in the authorization challenge request is useful only when the client expects that it will have to perform a redirect based authorization flow and also the AS supports PAR capabilities through the authorization_challenge_endpoint. I think this will be an edge case and given the spec mentions it supports all extensions applicable to the authorization endpoint I don’t see a major need to specifically mention these two parameters under this section. I think this could also cause confusion to implementers.

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

No branches or pull requests

1 participant