Skip to main content
OpenID Connect (OIDC) Discovery documents contain metadata about the (IdP). Adding discovery to your SDK to point your application to the ./wellknown endpoint to consume information about your IdP could help configure your integration with the IdP. Integrating OIDC discovery into your SDK provides: You can configure applications with the OpenID Connect (OIDC) discovery documents found at: https://{yourDomain}/.well-known/openid-configuration.

​
Sample response

​
Sample implementation

For example, this is how to configure OIDC middleware for Katana v3 (OWIN):
  1. Install the nuget package: Microsoft.Owin.Security.OpenIdConnect (v3.x.x)
  2. Go to App_Start\Startup.Auth.cs and replace your implementation with the following:

​
RSA algorithm for JWTs

The OIDC middleware does not support signed with symmetric keys. Make sure you configure your app to use the RSA algorithm using public/private keys.
  1. Go to Dashboard > Settings.
  2. Scroll down to Advanced Settings.
  3. Under the OAuth tab, set RS256 as Json Web Token(JWT) Signature Algorithm and click Save.
With this setting, Auth0 will issue JWTs signed with your private signing key. Your app will verify them with your public signing key.

​
Configure applications with OAuth 2.0 Authorization Server Metadata

If your application or SDK references the OAuth RFC-8414 Metadata specification, you can use the alias to fetch metadata about the IdP: /.well-known/oauth-authorization-server. For example, the Auth0 Model Context Protocol Server recommends all OAuth applications reference the OAuth Authorization Server Metadata specification.

​
Learn more

⌘I