Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

tba-router-wpt-verification

TBA · Tigrbl Auth

Checkout: 0.4.0.dev2 Python: >=3.10,<3.16 License: Apache-2.0 Layer: 80 routers PyPI version for tba-router-wpt-verification

Monthly PyPI downloads for tba-router-wpt-verification Evidence: verification

Authenticated remote WIT/WPT verification for a configured recipient.

Quick start

Mount build_wpt_verification_router(verifier=..., audience=..., authenticate=..., authorize_verification=...) on a TigrblApp. authenticate identifies the calling recipient service; the separate authorize_verification callback must explicitly allow that service to delegate verification for the configured audience. These checks precede proof validation.

POST /wpt/verify accepts:

{
  "workload_identity_token": "<original WIT>",
  "workload_proof_token": "<original WPT, without the WPT scheme prefix>",
  "token_headers": [{"name": "Txn-Token", "value": "<original token>"}]
}

token_headers is a list so duplicate original headers remain observable and are rejected when used as bindings. Do not collapse duplicates before forwarding. Caller authentication belongs in this API request's headers, separately from the submitted workload proof. Submitted audiences and trust configuration are rejected. The audience and required_token_headers are selected when mounting. Required headers must be present and cryptographically bound; clients cannot disable this policy by omitting a header. This strict presence policy is separate from the profile's optional bound_token_headers binding selector.

A successful response contains valid, subject, audience, proof_id, and expires_at. Missing/denied caller credentials return 401/403, malformed requests return 400, and invalid or replayed workload proofs return 401. Responses disable caching and do not echo tokens. An infrastructure exception fails the request; it never returns a successful verification decision.

Verification consumes replay state. Use the result once for the original request; do not preflight it and then verify the same proof again. The result authenticates the workload; the recipient still applies resource authorization. Transport this delegation over the deployment's authenticated confidential channel.

Build from the repository root:

uv build --wheel pkgs/80-routers/tba-router-wpt-verification

Verification

uv run --extra test pytest pkgs/120-tests/tba-tests-workload-composition/tests/test_wit_wpt_services.py

Metadata

Release files for tba-router-wpt-verification 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)

Source distribution for tba-router-wpt-verification 0.4.0.dev2
File Size Uploaded Provenance Actions
tba_router_wpt_verification-0.4.0.dev2.tar.gz 3.8 kB Without provenance Details for tba_router_wpt_verification-0.4.0.dev2.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for tba-router-wpt-verification 0.4.0.dev2
File Interpreter ABI Platform Actions
tba_router_wpt_verification-0.4.0.dev2-py3-none-any.whl Python 3 none any Details for tba_router_wpt_verification-0.4.0.dev2-py3-none-any.whl

Total release size: 9.1 kB

Release files / tba_router_wpt_verification-0.4.0.dev2.tar.gz

Download URL tba_router_wpt_verification-0.4.0.dev2.tar.gz
Size 3.8 kB
Tags Source
SHA-256 checksum
How to use checksums
a9d21d0c00d7b600ee2275715bc561253bf22b738fc0790d4a1f7cb203472e2f
BLAKE2b-256 checksum
How to use checksums
a1b5f390a7784370fb98e9c7a55340bbf8f1510ad7b8b15918218c3903b40e93
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / tba_router_wpt_verification-0.4.0.dev2-py3-none-any.whl

Download URL tba_router_wpt_verification-0.4.0.dev2-py3-none-any.whl
Size 5.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
af3a7f266be13c4df75e89c54b6fe871b70fef4955ea56d8829437b02bf10efd
BLAKE2b-256 checksum
How to use checksums
1b5b406aeb679c9a0092538066b21ffa43a07b4fc21f0033f6d196ede034968a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for tba-router-wpt-verification 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.

Release history Release notifications | RSS feed

This release
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page