Uses of Package
com.revetsec.oauth
Packages that use com.revetsec.oauth
Package
Description
OAuth 2.0 client flows and pure bearer presentation, challenge and protected-resource metadata helpers
(RFC 6749, RFC 7636, RFC 6750, RFC 9728).
Application contracts for OAuth authorization-server issuance.
OpenID Connect relying party support, composed on the OAuth 2.0 client pipeline (OpenID Connect Core 1.0).
-
Classes in com.revetsec.oauth used by com.revetsec.oauthClassDescriptionA raw access token returned by an AS.The outcome of a cached client-credentials token acquisition.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.Validates bearer access tokens for explicitly configured audiences.The outcome of OAuth callback completion.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.Known authorization-server metadata.Builds manually configured metadata.The outcome of parsing bounded provider metadata.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.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.An OAuth endpoint category used in redacted observer events.Fixed OAuth and OpenID Connect protocol errors for endpoint and checked authorization rejections.An OAuth request, response, validation or transport failure.Reasons for OAuth failures.Receives synchronous, caller-thread OAuth events.The outcome of one token revocation request.The outcome of one token request.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.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.
-
Classes in com.revetsec.oauth used by com.revetsec.oauth.serverClassDescriptionThe failed credential check.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).Access-token proof released only after all configured profile checks.
-
Classes in com.revetsec.oauth used by com.revetsec.oidcClassDescriptionA browser redirect and its pending authorization.The trusted callback delivery mode.A parsed browser authorization response.One OAuth client authentication strategy.Whether the RFC 9207 callback issuer is required.Fixed OAuth and OpenID Connect protocol errors for endpoint and checked authorization rejections.Reasons for OAuth failures.Receives synchronous, caller-thread OAuth events.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 secret refresh token.Scope, resource and additional form options for one token request.One token-endpoint success.