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

V51 OAuth: Add verification for PAR #2042

Open
TobiasAhnoff opened this issue Aug 31, 2024 · 3 comments
Open

V51 OAuth: Add verification for PAR #2042

TobiasAhnoff opened this issue Aug 31, 2024 · 3 comments
Assignees
Labels
1) Discussion ongoing Issue is opened and assigned but no clear proposal yet V51 Group issues related to OAuth _5.0 - prep This needs to be addressed to prepare 5.0

Comments

@TobiasAhnoff
Copy link

PAR is part of FAPI 2 requirements and the following verification is suggested to address PAR:

V51.2 Authorization Server

Verify that grant type 'code' is always used together with PAR requiring client authentication (for L1-L2 PAR is optional and could be used without client authentication). (L3)

@elarlang elarlang added the V51 Group issues related to OAuth label Aug 31, 2024
@tghosth tghosth added 1) Discussion ongoing Issue is opened and assigned but no clear proposal yet _5.0 - prep This needs to be addressed to prepare 5.0 labels Sep 2, 2024
@elarlang
Copy link
Collaborator

@TobiasAhnoff or @randomstuff - please explain, what security problem it solves?

@randomstuff
Copy link

The client can make sure that the user does not tamper with the content of the authorization request such as:

  • changing the value in a RAR request,
  • requiring different scopes than what the authorization server intended.

Moreover this aligns with FAPI 2.0?

@TobiasAhnoff
Copy link
Author

Yes, PAR closes a number of tampering issues (integrity protection for the auth request), see e g https://openid.bitbucket.io/fapi/fapi-2_0-security-profile.html#name-main-differences-to-fapi-10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1) Discussion ongoing Issue is opened and assigned but no clear proposal yet V51 Group issues related to OAuth _5.0 - prep This needs to be addressed to prepare 5.0
Projects
None yet
Development

No branches or pull requests

4 participants