liveBook · Manning

Openid configuration endpoint

As explained in Spring Security in Action, Second Edition

An OpenID configuration endpoint publishes an OpenID Connect provider's supported endpoints and protocol configuration metadata.

An OpenID configuration endpoint lets a client discover an authorization server’s supported endpoints and protocol metadata before starting an authorization flow. A GET request requires no authentication. section 14.2

http://localhost:8080/.well-known/openid-configuration

Request http://localhost:8080/.well-known/openid-configuration to discover the server’s default endpoint paths. section 14.2

Discovery before authorization

A client first reads the configuration, then uses the returned authorization endpoint to request a code and the token endpoint to exchange it for tokens.

How Spring Security in Action, Second Edition covers it

How deep it goes
Defines the discovery request and response metadata, but does not detail endpoint implementation.
Examples
Uses a localhost discovery URL, a JSON metadata response, and subsequent authorization-code requests.
What it assumes
Assumes familiarity with registered clients and authorization-code flows while demonstrating discovery before client requests.
What you can do after
Operate an authorization-code client by discovering endpoint paths and supported protocol capabilities.
How it connects
Connects authorization endpoints, token endpoints, JWKS endpoints, userinfo 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 Spring Security in Action, Second Edition. The section links point to the parts of the book it draws on.