Skip to content

Abblix.Oidc.Server.MinimalApi.Formatters Namespace

Classes
AuthorizationResponseFormatterMaps an encoded authorization response onto the wire DTO and delivers it as an Microsoft.AspNetCore.Http.IResult: a redirect (query/fragment), a form_post page, an interaction-page redirect, or a no-redirect error. Protocol-level decisions (parameter assembly, iss/scope gating, JARM packing) are made upstream by the core encoder.
BackChannelAuthenticationResponseFormatterFormats CIBA backchannel authentication results as Microsoft.AspNetCore.Http.IResult: a JSON success response, a 401 with a WWW-Authenticate challenge matching the client's scheme, a 403, or a 400 with the JSON error envelope.
CheckSessionResponseFormatterProduces the check-session iframe document, generating a per-request CSP nonce to protect the inline script.
ConfigurationResponseFormatterBuilds the OpenID Connect discovery document by enriching the core metadata with endpoint URLs resolved from the configured route templates and the current request's base URL, then returns it as a JSON Microsoft.AspNetCore.Http.IResult.
DeviceAuthorizationResponseFormatterFormats device authorization results (RFC 8628) as Microsoft.AspNetCore.Http.IResult: a JSON device-code response on success, or the JSON OAuth error on failure. The verification URIs, code lifetime and polling interval are taken from the configured device authorization options.
EndSessionResponseFormatterFormats end-session results as Microsoft.AspNetCore.Http.IResult: a front-channel-logout HTML page (with a per-response CSP nonce), a post-logout redirect, an empty 204, or the JSON OAuth error.
IntrospectionResponseFormatterFormats introspection results as Microsoft.AspNetCore.Http.IResult: a plain RFC 7662 JSON document, or, when the client registered introspection_signed_response_alg and requests it via Accept: application/token-introspection+jwt, a signed/encrypted JWT (RFC 9701); the OAuth error otherwise.
PushedAuthorizationResponseFormatterFormats pushed authorization request results as Microsoft.AspNetCore.Http.IResult. PAR is a server-to-server endpoint (RFC 9126): responses are always JSON and errors never redirect.
ReadClientResponseFormatterFormats a client-read result (RFC 7592 §2.1) as Microsoft.AspNetCore.Http.IResult: a 200 with the client configuration (its registration_client_uri filled in) on success, or the JSON OAuth error on failure.
RegisterClientResponseFormatterFormats dynamic client registration results (RFC 7591) as Microsoft.AspNetCore.Http.IResult: a 201 with the registered client configuration on success, or the JSON OAuth error on failure.
RegistrationClientUriBuilderBuilds the RFC 7592 registration_client_uri - the absolute URL of a client's configuration endpoint - from the current request's base URL and the configured client-management route, replacing the MVC integration's IUriResolver.
RemoveClientResponseFormatterFormats a client-removal result (RFC 7592 §2.3) as Microsoft.AspNetCore.Http.IResult: an empty 204 on success, or the JSON OAuth error on failure.
RevocationResponseFormatterFormats token revocation results as Microsoft.AspNetCore.Http.IResult: an empty 200 on success, or the RFC-compliant OAuth error on failure.
TokenResponseFormatterFormats token endpoint results as Microsoft.AspNetCore.Http.IResult: a JSON token response on success, or the RFC-compliant OAuth error (status, JSON envelope, WWW-Authenticate challenge, DPoP-Nonce) on failure.
UpdateClientResponseFormatterFormats a client-update result (RFC 7592 §2.2) as Microsoft.AspNetCore.Http.IResult: a 200 with the updated client configuration on success, or the JSON OAuth error on failure.
UserInfoResponseFormatterFormats UserInfo results as Microsoft.AspNetCore.Http.IResult: the plain claims JSON, or, when the client registered a userinfo_signed_response_alg, a signed (and optionally encrypted) JWT carrying the same claims (OpenID Connect Core 5.3.2). On failure it returns the RFC 6750 / RFC 9449 §7.1 challenge response that advertises both the DPoP and Bearer schemes.