liveBook · Manning

RegisteredClientRepository

As explained in Spring Security in Action, Second Edition

RegisteredClientRepository is a Spring Security Authorization Server interface for storing and retrieving registered OAuth clients and their configurations.

RegisteredClientRepository is the Spring Security Authorization Server contract for managing OAuth client credentials and configuration. An authorization server needs an implementation to register and retrieve client details. section 14.1 section 14.6

In-memory client registration

Define a RegisteredClient with clientId("client"), clientSecret("secret"), CLIENT_SECRET_BASIC authentication, the authorization_code grant, a redirect URI, and the openid scope, then expose an in-memory repository as a Spring bean.

How Spring Security in Action, Second Edition covers it

How deep it goes
Defines the implementation contract and demonstrates in-memory registration, without detailing persistent storage.
Examples
Uses an in-memory client with a secret, Basic authentication, authorization code, redirect URI, and openid scope.
What it assumes
Uses standard Spring configuration and RegisteredClient builder settings for client identity, authentication, grants, redirects, and scopes.
What you can do after
Build it from scratch by exposing a RegisteredClientRepository bean with configured client registrations.
How it connects
Connects client registration with OAuth 2 grant types, OpenID Connect scopes, UserDetailsService, and JWKSource.
Cover of Spring Security in Action, Second Edition
liveBookmanning.com
Read Spring Security in Action, Second Edition on liveBook Get the book at manning.com

Also explained in

Compare how 2 books explain RegisteredClientRepository →

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.