Uses of Package
com.revetsec.jose
Packages that use com.revetsec.jose
Package
Description
JSON Object Signing and Encryption: JWS signature verification and bounded RSA signing, JSON Web Keys and key sets, and JWT claims
validation (RFC 7515, RFC 7517, RFC 7519).
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.jose used by com.revetsec.joseClassDescriptionA rejected JOSE input: a token that
JwtValidatorrefused, or a JSON Web Key Set document thatJwks.fromJsonResult(String)rejected.Why a JOSE input was rejected.Receives events fromJwtValidatorandRemoteJwksSource, for metrics, logs and alerts.One usable public key from aJwks: an RSA, EC (P-256, P-384 or P-521) or Ed25519 key that passed every rule for verifying JWS signatures (seeJwkSkipReason).A JSON Web Key Set (RFC 7517 section 5): the usable public verification keys of a key set document, in document order.Why a key in a JSON Web Key Set is not used.The outcome of parsing a JSON Web Key Set document with the default size and key-count limits.Publishes an immutable snapshot of public verification keys without an OAuth authorization server, signing, storage, network access or background threads.Configures an immutable public key snapshot.An immutable HTTP response containing only public JWKS data.Where a validator gets the public keys that verify token signatures: a fixed key set (StaticJwksSource) or one fetched from a URI and kept up to date (RemoteJwksSource).Thrown when aRemoteJwksSourcehas no usable JSON Web Key Set for a call: the fetch failed, a recent failure is still suppressing fetches, the limit of two requests per cooldown held the call back, or the call's deadline ended while it waited for another caller's fetch.A JWS signature algorithm, named by itsalgheader value (RFC 7515 section 4.1.1, RFC 7518 section 3.1, RFC 8037 section 3.1 and RFC 9864).Signs compact JWS credentials with one application-owned key pair and one fixed algorithm.Configures one signing operation.Why signing failed.A JWT thatJwtValidator.validateResult(String)accepted: its signature verified with a trusted key, and its type, issuer, audience, lifetime and required claims passed.The claims of a validated JWT (RFC 7519 section 4).An immutable JWT claims set for signing (RFC 7519 section 4), with typed registered claims and JSON custom claims.Builds an outbound claims set.Immutable protected-header metadata for signing a JWT: its requiredtypeand optional key identifier and SHA-256 certificate thumbprint.Configures an immutable JWT signing header without signing or I/O.A supported JWT protected-headertypvalue used when signing a token.The outcome of JWT validation.Validates JWTs in the JWS compact serialization (RFC 7519, RFC 7515) signed with a public key, for one expected issuer.Builds aJwtValidator.An immutable public signing key for publication in a JSON Web Key Set (RFC 7517).Configures an immutable published public key.A JSON Web Key Set fetched from a URI and cached, such as an OpenID provider'sjwks_uri.Builds aRemoteJwksSource.A fixed set of verification keys, which never changes and is never fetched. -
Classes in com.revetsec.jose used by com.revetsec.oauthClassDescriptionWhy a JOSE input was rejected.Receives events from
JwtValidatorandRemoteJwksSource, for metrics, logs and alerts.Where a validator gets the public keys that verify token signatures: a fixed key set (StaticJwksSource) or one fetched from a URI and kept up to date (RemoteJwksSource).A JWS signature algorithm, named by itsalgheader value (RFC 7515 section 4.1.1, RFC 7518 section 3.1, RFC 8037 section 3.1 and RFC 9864).Signs compact JWS credentials with one application-owned key pair and one fixed algorithm. -
Classes in com.revetsec.jose used by com.revetsec.oauth.server
-
Classes in com.revetsec.jose used by com.revetsec.oidcClassDescriptionWhy a JOSE input was rejected.Receives events from
JwtValidatorandRemoteJwksSource, for metrics, logs and alerts.Where a validator gets the public keys that verify token signatures: a fixed key set (StaticJwksSource) or one fetched from a URI and kept up to date (RemoteJwksSource).A JWS signature algorithm, named by itsalgheader value (RFC 7515 section 4.1.1, RFC 7518 section 3.1, RFC 8037 section 3.1 and RFC 9864).The claims of a validated JWT (RFC 7519 section 4).