Skip to main content

Abblix.Oidc.Server.Features.Tokens.Formatters Namespace

Abblix.Oidc.Server

Abblix.Oidc.Server.Features.Tokens.Formatters Namespace

Classes
AuthServiceJwtFormatterProvides functionality to format and sign JSON Web Tokens (JWTs) specifically for use within the authentication service. This class processes tokens issued by the authentication service itself, including access tokens, refresh tokens and Registration Access Tokens generated during client registration via the dynamic registration API. It leverages signing and optional encryption to generate JWTs that authenticate and authorize internal service operations.
ClientJwtEncryptionThe encryption policy a caller hands to ClientJwtFormatter when formatting a client-addressed JWT. It makes explicit which registered client metadata governs encryption, so the formatter no longer has to infer it from the token type. Each client-JWT class (UserInfo, ID token, JARM authorization response, introspection) supplies its own policy via the static factories below.
ClientJwtFormatterProvides functionality to format JSON Web Tokens (JWTs) issued to clients by the authentication service. This class handles the signing of JWTs and, if configured, their encryption, based on the needs of each client.
Interfaces
IAuthServiceJwtFormatterSerializes a JsonWebToken minted by the authorization server itself (access tokens, refresh tokens, Registration Access Tokens) into a compact JWS form (RFC 7515) using the server's signing keys, optionally wrapping the result in a JWE (RFC 7516) when an encryption key is available.
IClientJwtFormatterSerializes a JWT addressed to a specific client (ID Token, Logout Token, etc.) into compact form: signed as a JWS (RFC 7515) with the server's signing key chosen by the JWT's header algorithm, then optionally wrapped in a JWE (RFC 7516) encrypted to the client's registered public key per the client's id_token_encrypted_response_alg/_enc metadata.