Uses of Package
com.revetsec.oauth.server
Packages that use com.revetsec.oauth.server
Package
Description
Application contracts for OAuth authorization-server issuance.
-
Classes in com.revetsec.oauth.server used by com.revetsec.oauth.serverClassDescriptionBounded single-process optional cache with timed interruptible locking and approximate LRU eviction.Trusted application authorization decision; it is not a verified authentication or token proof.Replacing decision builder.A library-created outcome.Caller-thread OAuth code issuer with authoritative online grant status.Mutable, non-thread-safe issuer configuration.Application-owned authoritative issuer persistence.Trusted bounded address resolution for opt-in client metadata retrieval.Thread-safe storage for bounded encrypted client-metadata carriers.Immutable bounded encrypted cache carrier.Fixed-diagnostic optional-cache failure, distinct from a miss or comparison conflict.The optional-cache failure reasons.Bounded opaque address for optional client-metadata storage.Immutable opt-in configuration for public client metadata documents.Builds an enabled policy; null property values reset defaults, except resolver and cache null clear required properties.Application-owned verification of a pre-registered confidential client's secret.Issuer-created grant facts supplied to the application's continuing authorization policy.Continuing application authorization policy, invoked outside store transactions at approval, code exchange and refresh.A library-created outcome.A library-created outcome.Trusted application-owned durable key lifecycle and distribution callback.Immutable application declaration of active, published and retained public keys.Builds a checked immutable declaration without signing or provider lookup.One application-owned RS256 signing key.A library-created outcome.Trusted registered-client authentication policy: public authentication or confidential client_secret_basic.Immutable application-owned client registration.Replacing, snapshotting registration builder.Application-owned lookup of trusted, pre-registered client configuration.The sealed issuer exception family.Fixed classifications; a later release may add values.A restricted view of a checked, pending browser interaction.Safe synchronous caller-thread issuer events.Fixed operation kinds, without request or application data.An immutable, bounded response prepared by the authorization server.Immutable factual issuer commitment, definitive refusal or uncertainty.Outcome of an atomic, durable issuer store commit.Immutable encrypted persistence carrier, not an authenticated authorization proof.Opaque issuer storage address.Issuer storage record kinds; a later release may add values.Coherent linearizable issuer entry/absence and admitted time metadata.The exact requested address, entry/absence and metadata from one atomic observation.The requested recovery/data incarnation cannot be served.No coherent authoritative observation could be established.Complete immutable issuer transaction, created only by the engine.An exact version or ABSENT predicate, engine-created and checked atomically with every other predicate.An engine-created PUT or REMOVE; PUT carries its exact key-matched entry and REMOVE carries no entry.The two mutation operations.The two explicit transaction modes.A library-created outcome.