Package com.revetsec.oauth
@NullMarked
package com.revetsec.oauth
OAuth 2.0 client flows and pure bearer presentation, challenge and protected-resource metadata helpers
(RFC 6749, RFC 7636, RFC 6750, RFC 9728). Resource-server validators are still being built.
It depends only on com.revetsec.jose, com.revetsec.json and the root package.
- Author:
- Mark Allen
-
ClassDescriptionA raw access token returned by an AS.The outcome of a cached client-credentials token acquisition.The endpoint returned a non-transient client error.The source returned a currently valid access token, from its cache or a completed renewal.Explicit access-token interoperability modes.Caller-thread resource events and inherited OAuth/JOSE events, without credentials or claims.A local bearer credential verdict, with fixed reasons and no token, claims or lower-layer exception retained.The failed credential check.The access-token verdict.The credential was rejected; no identity, claims, credential or exception is retained.The introspection endpoint rejected the request with a checked, nontransient client error.All configured access-token checks passed.Validates bearer access tokens for explicitly configured audiences.The outcome of OAuth callback completion.A bound callback reported access_denied after all pending-state and issuer checks.The pending store did not complete its operation.A local callback or pending-state security check rejected completion.A bound callback reported an authorization error after all pending-state and issuer checks passed.The endpoint returned a non-transient client error.The authorization flow completed once and returned endpoint tokens.A browser authorization error, reported only after pending-state and issuer checks pass.A browser redirect and its pending authorization.Per-authorization options.Mutable request-option builder.The trusted callback delivery mode.A parsed browser authorization response.The outcome of parsing a raw, unverified OAuth browser callback.A malformed, duplicate, oversized or split-channel callback.A syntactically parsed callback that remains unverified until transaction completion.Known authorization-server metadata.Builds manually configured metadata.The outcome of parsing bounded provider metadata.A rejected metadata document with no received payload.Checked metadata; the application still selects a trusted issuer.A bounded WWW-Authenticate Bearer value (RFC 6750 section 3 and RFC 9728 section 5).Mutable challenge configuration.RFC 6750 section 3.1 bearer errors and their recommended HTTP status codes.An unverified credential parsed from exactly one Authorization field (RFC 6750 section 2.1).The outcome of parsing materialized Authorization headers.No Authorization header was supplied.The supplied header values are malformed, duplicated or oversized.Exactly one header supplied a syntactically valid, unverified bearer credential.The sole audience of an OAuth client assertion.Supplies one immutable key and header snapshot per assertion POST.Immutable signer and protected-header identifiers selected together for one assertion.Configures one immutable signing snapshot without provider or signing calls.One OAuth client authentication strategy.Configures assertion audience and lifetime.A bounded caller-thread cache for confidential client-credentials access tokens.Configures a source without network I/O.Client-secret Basic encoding.A bounded, single-process pending-authorization store.Configures the store.Whether the RFC 9207 callback issuer is required.RFC9068 JWT bearer-access-token validator for exact issuer and explicitly configured audiences.Configures an immutable resource validator.OAuth 2.0 authorization-code, client-credentials, refresh and revocation client.Configures an OAuth client.A fixed, cause-free failure of configured assertion keys, signing, endpoint trust, discovery identity or issuer policy.An OAuth endpoint category used in redacted observer events.Fixed OAuth and OpenID Connect protocol errors for endpoint and checked authorization rejections.A token, revocation or UserInfo endpoint error.An OAuth request, response, validation or transport failure.Reasons for OAuth failures.Receives synchronous, caller-thread OAuth events.An authorization-server response is malformed or redirected.The outcome of one token revocation request.The endpoint returned a non-transient client error.The endpoint accepted the revocation request; RFC 7009 also accepts unknown tokens.The outcome of one token request.The endpoint returned a non-transient client error.The endpoint issued tokens.A network failure, interruption, attempt-limit hold or unavailable HTTP client.A pending authorization or OAuth security check failed.One pending browser authorization, including secret state, PKCE verifier and an OIDC nonce slot.Closed, value-free provider outcomes for saving a browser-bound pending authorization.A browser-bound source for completing one authorization.Storage for opaque, browser-bound pending authorization records.A pending-authorization store could not complete an operation.Application-configured protected-resource metadata (RFC 9728 sections 2 and 3).Mutable metadata configuration.A secret refresh token.Audience-checked RFC7662 JSON introspection using the supplied OAuth client settings.Configures required audiences and optional introspection policy; OAuth settings are inherited.Scope, resource and additional form options for one token request.Mutable builder for one token request.One token-endpoint success.RFC 7009 revocation token-type hint.Access-token proof released only after all configured profile checks.