Skip to main content

RequestObjectFetchAdapter Class

Abblix.Oidc.Server​

Abblix.Oidc.Server.Endpoints.Authorization.RequestFetching​

RequestObjectFetchAdapter Class​

Adapter class that implements IAuthorizationRequestFetcher to delegate the fetching and processing of request objects to an instance of IRequestObjectFetcher.

public class RequestObjectFetchAdapter : Abblix.Oidc.Server.Endpoints.Authorization.RequestFetching.IAuthorizationRequestFetcher

Inheritance System.Object → RequestObjectFetchAdapter

Implements IAuthorizationRequestFetcher

Constructors​

RequestObjectFetchAdapter(IRequestObjectFetcher) Constructor​

Adapter class that implements IAuthorizationRequestFetcher to delegate the fetching and processing of request objects to an instance of IRequestObjectFetcher.

public RequestObjectFetchAdapter(Abblix.Oidc.Server.Features.RequestObject.IRequestObjectFetcher requestObjectFetcher);

Parameters​

requestObjectFetcher IRequestObjectFetcher​

The request object fetcher responsible for fetching and processing the JWT request object.

Methods​

RequestObjectFetchAdapter.FetchAsync(AuthorizationRequest) Method​

Fetches and processes the authorization request by delegating to the request object fetcher. The request object JWT is validated and its claims are merged into the authorization request. Client identification is performed using the request parameter, JWT issuer claim, or JWT client_id claim, with validation ensuring all present sources match.

public System.Threading.Tasks.Task<Abblix.Utils.Result<Abblix.Oidc.Server.Model.AuthorizationRequest,Abblix.Oidc.Server.Endpoints.Authorization.Interfaces.AuthorizationRequestValidationError>> FetchAsync(Abblix.Oidc.Server.Model.AuthorizationRequest request);

Parameters​

request AuthorizationRequest​

The authorization request to be processed.

Implements FetchAsync(AuthorizationRequest)

Returns​

System.Threading.Tasks.Task<Abblix.Utils.Result<AuthorizationRequest,AuthorizationRequestValidationError>>
A task that returns a Abblix.Utils.Result<> which either represents a successfully processed request with merged JWT claims or an error indicating issues with the request object validation (invalid JWT, client identification failure, or claim mismatch).