Package com.revetsec.oidc
@NullMarked
package com.revetsec.oidc
OpenID Connect relying party support, composed on the OAuth 2.0 client pipeline (OpenID Connect Core 1.0).
It depends only on com.revetsec.oauth, com.revetsec.jose, com.revetsec.json and
the root package.
- Author:
- Mark Allen
-
ClassDescriptionAn ID token whose signature, registered claims and OIDC checks have all passed.One fully validated code-flow authentication.Per-login OIDC options (OpenID Connect Core section 3.1.2.1).Mutable per-login option builder.The outcome of OIDC 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 failed.A bound callback reported an authorization error after all pending-state and issuer checks passed.The endpoint returned a non-transient client error.The ID token failed validation.The shared authorization checks and all ID-token profile checks passed.OpenID Connect authorization-code relying party.Mutable OIDC client configuration.Explicit per-client OIDC relaxations.An OpenID Connect validation failure.Exact issuer validation or the fixed Microsoft Entra common/organizations v2.0 trust policy.A fixed configuration, preparation, storage or runtime failure in RP-Initiated Logout.Fixed reasons.An explicitly retained logout credential bound to the original OIDC continuity reference.Structure-only restoration of a logout credential from trusted or typed sealed storage.A structurally consistent hint, not an authentication proof.A stored form could not be opened or structurally restored.A prepared browser request, not provider-session termination or authenticated identity.A correlated browser return or fixed rejection.Value-free callback rejection reasons.The callback did not satisfy the selected correlation profile.Correlation succeeded.Receives caller-thread OIDC events and the inherited OAuth/JOSE endpoint events.OpenID provider metadata (OpenID Connect Discovery 1.0 section 3), from discovery or explicit configuration.Mutable explicit provider configuration.The outcome of parsing bounded provider metadata.A rejected metadata document with no received payload.Checked metadata; the application still selects a trusted issuer.Checked values from one refresh, released after any returned ID token passes signature, profile and original-session continuity checks.The result of an OIDC token refresh.A local OIDC check rejected the operation.The endpoint returned a non-transient client error.The refresh completed and any returned ID token passed continuity checks.Continuity reference for refresh and future logout.The outcome of parsing a stored OIDC continuity reference.The stored reference could not be parsed or opened.A structurally valid continuity reference was parsed.UserInfo whose subject exactly matches a verified authentication.The outcome of a UserInfo request.A local OIDC check rejected the operation.The endpoint returned a non-transient client error.The UserInfo response passed all configured identity and profile checks.An ID token, UserInfo response or refresh continuity check failed.Fixed OIDC validation reasons.One bounded pending logout correlation record, separate from login.A typed browser-bound source for logout return correlation.