This release is a pre-release and may not be stable for production use.
tigrbl-pushed-authorization-capability
Layer-40 orchestration for persisting an already normalized and authenticated pushed authorization request.
Injected dependencies
A durable request-URI creation callable is required. A durable audit callable is optional. Both may be synchronous or asynchronous.
Operations and readiness
push_authorization_request is required; record_audit_event is optional.
Readiness follows the persistence binding, and the report exposes audit
availability separately.
Protocol consumers
The layer-50 OAuth package maps RFC 9126 PAR to this capability. OIDC and HAIP consume it through their configured OAuth/FAPI compositions where applicable.
Non-goals
This package does not parse HTTP, authenticate clients, validate request objects/DPoP, choose FAPI policy or RFC errors, open sessions, or own state.
Metadata
Release files for tba-capability-authorization-request-staging 0.4.0.dev2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tba_capability_authorization_request_staging-0.4.0.dev2.tar.gz | 2.4 kB | Without provenance | Details for tba_capability_authorization_request_staging-0.4.0.dev2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tba_capability_authorization_request_staging-0.4.0.dev2-py3-none-any.whl | Python 3 | none | any | Details for tba_capability_authorization_request_staging-0.4.0.dev2-py3-none-any.whl |
Total release size: 5.7 kB
Security for tba-capability-authorization-request-staging 0.4.0.dev2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.