authweave-workload

Framework-neutral authentication for registered service applications and service, workload, or agent principals. Version 7 supports registered X.509 credentials, direct mTLS, mTLS-bound access tokens, DPoP-bound access tokens issued by an external OAuth Authorization Server, SPIFFE X.509-SVID resource-server verification, RFC 7662 mTLS- or DPoP-bound opaque-token introspection, and sender-constrained outbound RFC 8693 token exchange. Issuer-specific payment authority is available through the strict RFC 9396 payment authorization-details profile.

uv add 'authweave-workload[mtls,jwt,dpop,spiffe,introspection,token-exchange]'

The base package never accepts or stores private keys and imports no web framework, ORM, or cryptography implementation. Optional DPoP verification lives behind authweave-workload[dpop] and never mints tokens. Optional SPIFFE verification lives behind authweave-workload[spiffe] and never registers short-lived SVIDs by thumbprint (see ADR 0006). Optional introspection lives behind authweave-workload[introspection] (see ADR 0007). Merchant notes: docs/merchant/dpop.md, docs/merchant/spiffe.md, docs/merchant/introspection.md, docs/merchant/token-exchange.md. The payment profile and application guard are documented in docs/merchant/authorization-details.md.

Lifecycle mutations require a verified actor, a correlation ID, and an application recorder that writes the security event in the same transaction. X.509 registration accepts only opaque CertificateMetadata returned by validate_public_certificate; it cannot be built from unchecked fields. Custom stores raise StoreOwnerStateConflictError when concurrent owner revalidation rejects a principal or credential write; the lifecycle service maps that typed conflict to LifecycleConflictError.

The optional Litestar adapter accepts Envoy evidence only over an explicitly trusted TCP peer or permission-restricted Unix socket. Envoy's hex certificate fingerprint is normalized to canonical base64url, while revocation freshness comes from application-trusted CRL/control-plane metadata rather than an inbound request header.

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

authweave_workload-7.3.0.tar.gz (62.1 kB view details)

Uploaded Aug 8, 2026 Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

The dropdown lists show the available interpreters, ABIs, and platforms. Enable javascript to be able to filter the list of wheel files.

authweave_workload-7.3.0-py3-none-any.whl (78.6 kB view details)

Uploaded Aug 8, 2026 Python 3

File details

Details for the file authweave_workload-7.3.0.tar.gz.

File metadata

Download URL: authweave_workload-7.3.0.tar.gz
Upload date: Aug 8, 2026
Size: 62.1 kB
Tags: Source
Uploaded using Trusted Publishing? Yes
Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for authweave_workload-7.3.0.tar.gz
Algorithm	Hash digest
SHA256	`2fb1922674b1e1d5ff62e08aca28d133edd37a842bdece58153cf2b1bd985c82`
MD5	`d23f61cccc9126d35968bab79d63d102`
BLAKE2b-256	`f8d234f37b64748ce9130b0d88189734dfa64ede3edaa07c59916fa01ed74b9e`

See more details on using hashes here.

Provenance

The following attestation bundles were made for authweave_workload-7.3.0.tar.gz:

Publisher: 3_release.yml on ZYLVEXT/litestar-auth

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Statement:
- Statement type: https://in-toto.io/Statement/v1
- Predicate type: https://docs.pypi.org/attestations/publish/v1
- Subject name: authweave_workload-7.3.0.tar.gz
- Subject digest: 2fb1922674b1e1d5ff62e08aca28d133edd37a842bdece58153cf2b1bd985c82
- Sigstore transparency entry: 2379156466
- Sigstore integration time: Aug 8, 2026
Source repository:
- Permalink: ZYLVEXT/litestar-auth@e4bfdaf136157d0e4bbcf21eed8516343faa2ca9
- Branch / Tag: refs/tags/7.3.0
- Owner: https://github.com/ZYLVEXT
- Access: public
Publication detail:
- Token Issuer: https://token.actions.githubusercontent.com
- Runner Environment: github-hosted
- Publication workflow: 3_release.yml@e4bfdaf136157d0e4bbcf21eed8516343faa2ca9
- Trigger Event: workflow_dispatch