Skip to main content

Abblix.Oidc.Server.Features.RichAuthorizationRequests Namespace

Abblix.Oidc.Server​

Abblix.Oidc.Server.Features.RichAuthorizationRequests Namespace​

Classes
AuthorizationDetailDescriptorHost-renderable description of a single RFC 9396 authorization_details entry, produced by BuildConsentDescriptorAsync(AuthorizationDetail, ClientInfo, CancellationToken). Surfaces a structured, localisable shape the consent UI can render directly -- without the host having to inspect the per-type JSON payload itself. Validators that do not override the default implementation return null, and the host is expected to fall back to a raw JSON dump.
ServiceCollectionExtensionsService-collection extensions for the RFC 9396 Rich Authorization Requests feature.
Interfaces
IAuthorizationDetailsMetadataProviderDiscovery metadata contributor for the RFC 9396 Rich Authorization Requests feature. Sources the set of authorization_details types the server supports, projected from the same keyed-DI registry that request-time dispatch uses — single source of truth for «what does this server understand».
IAuthorizationDetailsPolicySingle request-time entry point for the RFC 9396 authorization_details policy: per-client allowlist (§5.1) plus per-type composite dispatch (§5). Endpoint-side adapters delegate here so /authorize, /par, CIBA and device-flow share one policy source.
IAuthorizationDetailValidatorValidates a single RFC 9396 authorization_details entry whose type value matches the implementation. Hosts register one implementation per supported type via AddAuthorizationDetailValidator<TValidator>(this IServiceCollection, string); the composite IAuthorizationDetailsPolicy dispatches each request entry to the implementation keyed by the entry's type value.