Governance for resource-server validation of JWT and opaque access tokens, introspection, revocation, caching, mTLS, DPoP, policy-context mapping, failure, and audit evidence.
This repository is an installable SSOT Registry governance pack. It packages immutable ADR and SPEC documents for explicit, operator-approved downstream synchronization.
Short answer: access-token-validation-governance-pack is an installable SSOT governance pack for Access Token Validation. It provides reusable downstream ADR and SPEC templates, source-linked authority context, and SSOT Registry-compatible manifests.
Use this package when a downstream repository needs governed decisions and implementation-ready requirements for access token validation, without copying those requirements into adjacent governance packs.
- Installable Python package:
access-token-validation-governance-pack - GitHub package repository:
groupsum/access-token-validation-governance-pack - Import package:
access_token_validation_governance_pack - 3 portable downstream ADR templates for governed decisions.
- 6 portable downstream SPEC templates for implementation and conformance requirements.
- SSOT Registry-compatible metadata, manifests, hashes, reservation ownership, and compatibility declarations.
- Pack ID:
pack:access-token-validation - PyPI package:
access-token-validation-governance-pack - Import package:
access_token_validation_governance_pack - GitHub repository: groupsum/access-token-validation-governance-pack
- Reservation owner:
extension-pack:access-token-validation-governance-pack - Python compatibility:
>=3.10,<3.15 - SSOT Registry schema:
>=0.4.0 - SSOT pack contract:
>=0.2.17,<0.3.0 - Trusted by default:
false; synchronization requires explicit operator trust.
Access Token Validation
- RFC 9068: JWT Profile for OAuth 2.0 Access Tokens
- RFC 7662: OAuth 2.0 Token Introspection
- RFC 9449: Demonstrating Proof of Possession
- RFC 8705: OAuth 2.0 Mutual-TLS Client Authentication
adr:resource-servers-own-access-token-validation- Resource Servers Own Access Token Validationadr:token-claims-are-validated-authority-inputs-not-permissions- Token Claims Are Validated Authority Inputs Not Permissionsadr:sender-constrained-token-policy-is-explicit- Sender Constrained Token Policy Is Explicit
spc:jwt-access-token-validation-contract- JWT Access Token Validation Contractspc:opaque-token-introspection-contract- Opaque Token Introspection Contractspc:token-revocation-expiration-and-cache-contract- Token Revocation Expiration And Cache Contractspc:mtls-and-dpop-sender-constraint-contract- mTLS And DPoP Sender Constraint Contractspc:token-to-policy-context-mapping-contract- Token To Policy Context Mapping Contractspc:token-validation-audit-and-failure-contract- Token Validation Audit And Failure Contract
uv add access-token-validation-governance-pack
uv add ssot-registry access-token-validation-governance-packThe pack is not trusted implicitly. Inspect and preflight it before explicitly approving synchronization:
uvx --from ssot-registry ssot pack inspect access_token_validation_governance_pack
uvx --from ssot-registry ssot pack preflight . access_token_validation_governance_pack --all
uvx --from ssot-registry ssot pack sync . access_token_validation_governance_pack --all --trust --yes
uvx --from ssot-registry ssot validate .Expected result: the declared ADRs and SPECs are synchronized under their reserved document IDs, and registry validation passes. Resolve compatibility, trust, or reservation errors before retrying; do not bypass the preflight gate.
from access_token_validation_governance_pack import load_document_manifest, read_packaged_document_text
adr_manifest = load_document_manifest("adr")
spec_manifest = load_document_manifest("spec")
text = read_packaged_document_text("spec", "SPEC-2000-jwt-access-token-validation-contract.yaml")- GitHub package repository: groupsum/access-token-validation-governance-pack
- PyPI package: access-token-validation-governance-pack
- SSOT Registry: ssot-registry
- SSOT pack contracts: ssot-pack-contracts
This package is the canonical owner of the access token validation governance surfaces represented by its packaged ADRs and SPECs. Adjacent packs may define integration profiles, but must reference these document identities instead of restating their normative requirements.