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.

Sign up for GitHub

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

Jump to bottom

OAuth 2.1 compliance regarding PKCE and client secret #254

Open
stebenz opened this issue Dec 6, 2022 · 0 comments
Open

OAuth 2.1 compliance regarding PKCE and client secret #254

stebenz opened this issue Dec 6, 2022 · 0 comments
Labels
backend enhancement New feature or request go Pull requests that update Go code op pkg/op issues

Comments

@stebenz
Copy link
Contributor

stebenz commented Dec 6, 2022 •
edited by muhlemmer

Is your feature request related to a problem? Please describe.
The current definition of OAuth 2.1 expects a client secret when a confidential app is used in combination with PKCE.

Describe the solution you'd like
Check of client secret if PKCE flow is used when app is typed as confidential.

Describe alternatives you've considered
Split of compliance with a different version, to bet at least different from the new version of OAuth.

Additional context

https://datatracker.ietf.org/doc/html/draft-ietf-oauth-v2-1-09#authorization_codes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
backend enhancement New feature or request go Pull requests that update Go code op pkg/op issues
Projects
Product Management
Status: 📨 Product Backlog
Milestone
No milestone
Development

No branches or pull requests
4 participants
@muhlemmer @livio-a @hifabienne @stebenz