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

Authorization Server Metadata and Dynamic Client Registration support #298

Open
zecakeh opened this issue Jan 19, 2025 · 0 comments
Open

Comments

@zecakeh
Copy link

zecakeh commented Jan 19, 2025

Hi, I wondered if there was any interest to add support for those two OAuth 2.0 RFCs:

  1. Authorization Server Metadata (RFC8414): The main work would probably be to have a deserializable type for the metadata, since there is not mandatory endpoint to use to request it. It could even be used to build the Client, like Client::from_provider_metadata() in openidconnect. It would be very close to the ProviderMetadata from openidconnect, except that the required fields are different, like jwks_uri is not required for OAuth.
  2. Dynamic Client Registration (RFC7591): this is one is a proper request with the registration_uri endpoint but the main work will probably be the type for the client metadata too. Here the ClientMetadata looks like it could fit.

Since openidconnect depends on this crate, maybe there can be a way to create the metadata types here and reuse them in openidconnect so they can be extended if necessary?

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