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

Add OAuth 2.0 Pushed Authorization Requests support in the OpenID module #17594

Open
kevinchalet opened this issue Mar 10, 2025 · 1 comment
Open

Comments

@kevinchalet
Copy link
Member

OpenIddict 6.1.0 introduced full support for OAuth 2.0 Pushed Authorization Requests in both the client and server stacks: https://documentation.openiddict.com/configuration/pushed-authorization-requests.

While OC just migrated to OpenIddict 6.1.0, that feature is not currently enabled. Since it drastically improves the security level of interactive flows for confidential clients, we should definitely consider supporting it.

My recommendations:

  • Enable the OAuth 2.0 PAR Endpoint by default.
  • Add a data migration updating all the existing applications allowed to use the code/implicit/hybrid flows to also allow them to use the new PAR endpoint (some clients - like the MSFT OIDC client or OpenIddict - will automatically use PAR-enabled flows when the PAR endpoint is enabled, so if a client is not allowed to use that endpoint, an error will be returned).
  • Update the UpdateDescriptorFromSettings() extension to support handling the PAR endpoint permission.
  • Add an option allowing to force a specific application to use PAR in the application create/edit views.
  • Add a global option allowing to force all clients to use PAR in the server options.
Copy link
Contributor

We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).

This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.

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

No branches or pull requests

1 participant