Skip to main content

Abblix.Oidc.Server.Endpoints.Introspection.Interfaces Namespace

Abblix.Oidc.Server​

Abblix.Oidc.Server.Endpoints.Introspection.Interfaces Namespace​

Classes
IntrospectionSuccessServer-side model of the introspection response defined by RFC 7662 §2.2: a Boolean active flag and, when active, the token's metadata claims. Hosts may extend the JSON via additional top-level members; cross-domain extensions should be listed in the IANA "OAuth Token Introspection Response" registry (RFC 7662 §3.1).
IntrospectionSuccess.ParametersWire-level member names of the introspection response, as registered in the IANA "OAuth Token Introspection Response" registry (RFC 7662 §3.1).
ValidIntrospectionRequestOutput of IIntrospectionRequestValidator handed to the processor: pairs the original request with either the parsed token (active branch) or a null token (inactive branch produced via InvalidToken(IntrospectionRequest, ClientInfo), used so token-level failures flow through the same processing path without disclosing why per RFC 7662 §2.2).
Interfaces
IIntrospectionHandlerDefines the contract for handling introspection requests to determine the current state and validity of OAuth 2.0 tokens, such as access tokens or refresh tokens.
IIntrospectionRequestProcessorBuilds the RFC 7662 introspection response for an already-validated request: returns active=true with claims for a live token, or active=false alone when the token is missing, expired, revoked, or issued to a different client (§2.2).
IIntrospectionRequestValidatorAuthenticates the calling client (RFC 7662 §2.1, "the protected resource calls the introspection endpoint using an HTTP request") and validates the supplied token. Implementations are expected to coerce token problems (expired, signed by a different issuer, audience mismatch, issued to another client) into a non-disclosing active=false result via InvalidToken(IntrospectionRequest, ClientInfo).