What is OpenID discovery endpoint?
Also referred to as the “well-known endpoint,” the discovery document is a set of OpenID Connect values that can be retrieved by OIDC clients; it’s the discovery document that enables OIDC clients to configure themselves in order to be able to access your implementation of Hosted Login.
What is a discovery endpoint?
The discovery endpoint can be used to retrieve metadata about your IdentityServer – it returns information like the issuer name, key material, supported scopes etc.
How do I find my well-known OpenID-configuration?
GET /. well-known/openid-configuration
- Authorization Roles/Permissions: Anyone can run this operation.
- Request URL https://accounts.google.com/.well-known/openid-configuration.
- Sample request headers Accept: application/json.
- Sample request body.
How do I change my well-known OpenID-configuration?
Steps
- Edit the openid-configuration. template. json file, located in the /pingfederate/server/default/conf/template directory, to specify the desired information to be returned by the OpenID Provider configuration endpoint.
- Save your changes. Template customization does not require a restart of PingFederate.
What is a discovery URL?
A Discovery URL is a URL adorned with a use type string. A Discovery URL can point to a “homepage” for the business, an XSD Schema that describes the business, or to another type of file describing the business or its services.
What can the discovery endpoint be used for?
The discovery endpoint can be used to retrieve metadata about your IdentityServer – it returns information like the issuer name, key material, supported scopes etc. See the spec for more details.
Where to find the discovery endpoint in identityserver4?
The discovery endpoint is available via /.well-known/openid-configuration relative to the base address, e.g.: You can use the IdentityModel client library to programmatically access the discovery endpoint from .NET code. For more information check the IdentityModel docs.
Where can I find the userinfo endpoint?
We do not recommend hard-coding the UserInfo endpoint in your app – use the OIDC discovery document to find this endpoint at runtime instead. As part of the OpenID Connect specification, the UserInfo endpoint is often automatically called by OIDC compliant libraries to get information about the user.
Is the Microsoft identity platform userinfo endpoint standards compliant?
As part of the OpenID Connect specification, the UserInfo endpoint is often automatically called by OIDC compliant libraries to get information about the user. Without hosting such an endpoint, the Microsoft identity platform would not be standards compliant and some libraries would fail.