liveBook · Manning

Openid configuration endpoint

As explained in Software Security for Developers

An OpenID configuration endpoint is a standardized endpoint that publishes an identity provider's OpenID Connect metadata and service endpoints.

An OpenID configuration endpoint publishes an identity provider’s OpenID Connect metadata, including the service endpoints a client needs for authorization and token issuance. Clients retrieve it before starting an authorization code flow, rather than hard-coding those URLs. section 12.3

Discovering the provider endpoints

For an identity provider running on localhost:9000, request http://localhost:9000/.well-known/openid-configuration. The response identifies the authorization endpoint at /oauth2/authorize and the token endpoint at /oauth2/token. The client can then use those discovered URLs to obtain an authorization code and exchange it for tokens. section 12.3

How Software Security for Developers covers it

How deep it goes
Defines the well-known path and key response fields, then leaves authorization requests and token exchange to subsequent steps.
Examples
Uses localhost:9000 discovery metadata containing /oauth2/authorize and /oauth2/token.
What it assumes
Uses identity provider, client application, authorization code, and token terminology without detailing those concepts from first principles.
What you can do after
Operate an OIDC client by retrieving provider metadata and using its discovered authorization and token endpoints.
How it connects
Connects OpenID Connect with identity providers, authorization endpoints, token endpoints, and authorization code grants.

Also explained in

Compare how 2 books explain openid configuration endpoint →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Software Security for Developers. The section links point to the parts of the book it draws on.