Stores

Stores in IdentityServer are the persistence layer abstractions responsible for managing various types of data needed for the authentication and authorization processes. They provide interfaces to store and retrieve configuration and operational data.

Configuration Stores

Configuration stores manage the relatively static data that defines how IdentityServer behaves:

Store	Purpose
IClientStore	Client application registrations
IResourceStore	API resources, API scopes, and identity resources
IIdentityProviderStore	Dynamic external identity providers
ICorsPolicyService	CORS origin validation for clients

Operational Stores

Operational stores manage transient, runtime data that supports active authentication flows:

Store	Purpose
IPersistedGrantStore	Authorization codes, refresh tokens, reference tokens, and user consent
IDeviceFlowStore	Device authorization grant data
IBackChannelAuthenticationRequestStore	CIBA authentication requests
IPushedAuthorizationRequestStore	Pushed Authorization Requests (PAR)
IServerSideSessionStore	Server-side user sessions
ISigningKeyStore	Automatic key management signing keys

Key Management Stores

These stores provide signing and validation keys to the runtime:

Store	Purpose
ISigningCredentialStore	Provides the active signing credential for token signing
IValidationKeysStore	Provides all public keys for token validation (published via JWKS)

In-Memory Implementations

IdentityServer provides default in-memory implementations suitable for development and testing. These are registered via the DI extension methods:

builder.Services.AddIdentityServer()
    .AddInMemoryClients(Config.Clients)
    .AddInMemoryApiScopes(Config.ApiScopes)
    .AddInMemoryIdentityResources(Config.IdentityResources);

For production environments, use the Entity Framework Core integration or implement custom stores using your preferred database technology.