client-attestation-sdk 0.2.0__tar.gz

client_attestation_sdk-0.2.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

client_attestation_sdk-0.2.0/PKG-INFO

@@ -0,0 +1,157 @@
+Metadata-Version: 2.4
+Name: client-attestation-sdk
+Version: 0.2.0
+Summary: Client-side builder SDK for OAuth Attestation-Based Client Authentication
+Author: ID Partners Pty Ltd
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/ID-Partners/client-attestation-sdk
+Project-URL: Source, https://github.com/ID-Partners/client-attestation-sdk/tree/main/python
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Security
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: pyjwt>=2.8
+Requires-Dist: cryptography>=42
+Provides-Extra: test
+Requires-Dist: pytest>=7; extra == "test"
+Requires-Dist: pytest-cov>=5; extra == "test"
+Provides-Extra: httpx
+Requires-Dist: httpx>=0.24; extra == "httpx"
+Provides-Extra: requests
+Requires-Dist: requests>=2.28; extra == "requests"
+Provides-Extra: aws
+Requires-Dist: boto3; extra == "aws"
+Dynamic: license-file
+
+# client-attestation-sdk (Python)
+
+Client-side builder for **OAuth Attestation-Based Client Authentication**
+(draft-ietf-oauth-attestation-based-client-auth). Mints the Client Attestation JWT (attester side) and the
+PoP / DPoP proofs + request headers (client side). Depends only on `pyjwt` + `cryptography`.
+
+Part of the [client-attestation-sdk](../README.md) monorepo; wire-compatible with the Java,
+TypeScript, and Go ports.
+
+## Install
+
+Not on PyPI yet. Install from a clone of this repository:
+
+```bash
+pip install -e '.[test]'
+```
+
+## Use
+
+```python
+from client_attestation_sdk import (
+    SigningKeyPair, ClientAttestationBuilder, ClientAttestationCredential,
+)
+
+# Attester issues the attestation, binding the client's public instance key
+attester = SigningKeyPair.generate("ES256")
+attestation = (
+    ClientAttestationBuilder(attester, "https://attester.example.com")
+    .client_id("https://rp.example.com")
+    .confirmation_jwk(client_instance_public_jwk)
+    .expires_in(300)
+    # optional: .authorization_details(...) / .workload(...) / .operator(sub, issuer=None) —
+    # operator names who's accountable for running the client (RFC 8693 may_act-shaped; an
+    # assertion, not proof of authorisation), distinct from client_id and from the principal.
+    .build()
+)
+
+# Client mints a fresh proof per token request
+instance = SigningKeyPair.from_jwk(my_instance_private_jwk, "ES256")
+cred = ClientAttestationCredential(attestation, instance)
+
+headers = cred.pop_headers("https://rp.example.com", "https://as.example.com")   # PoP-JWT mode
+# or
+headers = cred.dpop_headers("POST", "https://as.example.com/as/token.oauth2")    # DPoP combined mode
+# -> {"OAuth-Client-Attestation": "...", "OAuth-Client-Attestation-PoP" | "DPoP": "..."}
+```
+
+The one-call `ClientAttestation` orchestration class (see the [root README](../README.md#get-a-token-in-one-call))
+wraps this: `ClientAttestation(host, pop_method="dpop_combined")` switches it to DPoP mode, and a fetched
+challenge is carried through automatically as the PoP JWT's `challenge` claim or the DPoP proof's `nonce`
+claim, whichever mode is active.
+
+In DPoP mode the AS can issue a DPoP-bound token (`token_type: DPoP`). Use `ca.request_headers(method, url)`
+to get `Authorization: DPoP <token>` plus a fresh `DPoP` proof (with `ath` and any nonce the resource asked
+for), or `ca.requests_auth()` / `ca.httpx_auth()`, which also re-send once on a `use_dpop_nonce` challenge.
+Bearer tokens get just the `Authorization` header, as before.
+
+Other options on `ClientAttestation`:
+
+- `require_challenge=True` (default) - if the attester advertises a challenge endpoint and it fails, the flow
+  fails rather than minting without a challenge. `False` restores the old lenient behaviour.
+- `allow_insecure=False` (default) - `pf_host` and the discovered endpoints must be https, except loopback.
+- `trace=[...]` with `trace_redact=True` (default) - each wire call is recorded as a shell-quoted curl string
+  with every credential replaced by `<redacted:N bytes>`. `trace_redact=False` records them verbatim - for
+  local debugging only.
+
+`CLIENT_ATTESTATION_TOKEN_FILE` or `SPIFFE_ENDPOINT_SOCKET` set to a path that does not exist now raises
+`EvidenceNotFound` naming the variable, instead of falling through to the next evidence source.
+
+## Token validator
+
+The same distribution ships a resource-server validator (`token_validator`) — the side that *receives* and
+checks a token:
+
+```python
+from token_validator import AccessTokenValidator, ValidatorConfig
+
+validator = AccessTokenValidator(ValidatorConfig(
+    issuer="https://issuer.example.com", audiences=["https://api.example.com"],
+    jwks_uri="https://issuer.example.com/jwks", required_scopes=["read"]))
+
+result = validator.validate(access_token)          # signature + iss/exp/nbf + audience + scope
+if result.valid:
+    print(result.subject, result.scopes)
+else:
+    print(result.error)                            # e.g. "expired", "insufficient_scope"
+
+# optional RFC 7662 introspection (opaque tokens / revocation):
+result = validator.validate_active(access_token)
+```
+
+## SPIFFE workload identity → attestation bridge
+
+`client_attestation_sdk.spiffe` is a lightweight, standards-shaped stand-in for a SPIRE **agent**'s
+Workload API. It attests a workload by selector match and issues a **JWT-SVID** (`sub` = the SPIFFE ID,
+signed by the trust domain), alongside the workload's **attested attributes** — which then become the
+`workload` claim of a Client Attestation, so the AS discloses SPIFFE-attested attributes instead of static
+metadata. Maps 1:1 onto real SPIRE later; only the transport differs.
+
+```python
+from client_attestation_sdk import SpiffeAgent, SigningKeyPair, ClientAttestationBuilder, to_workload_claim
+
+agent = SpiffeAgent("banking.demo", SigningKeyPair.generate("ES256"))
+agent.register({"docker:label:app": "payment-agent"}, "payment-agent",
+               {"region": "emea", "entitlements": ["initiate_payment"]})
+
+svid = agent.fetch_jwt_svid({"docker:label:app": "payment-agent"}, audience="https://as.example.com")
+attestation = (ClientAttestationBuilder(attester, "https://attester.example.com")
+               .client_id(svid.spiffe_id).confirmation_key(instance)
+               .workload(to_workload_claim(svid))          # SPIFFE ID + attested attributes + the SVID
+               .expires_in(300).build())
+```
+
+Runnable end to end: `PYTHONPATH=src python3 examples/spiffe_bridge.py`. Verify a JWT-SVID against the
+trust bundle with `verify_jwt_svid(token, agent.trust_bundle(), audience, trust_domain)`.
+
+## Test
+
+```bash
+pip install -e .[test]
+pytest
+```

client_attestation_sdk-0.2.0/README.md

@@ -0,0 +1,122 @@
+# client-attestation-sdk (Python)
+
+Client-side builder for **OAuth Attestation-Based Client Authentication**
+(draft-ietf-oauth-attestation-based-client-auth). Mints the Client Attestation JWT (attester side) and the
+PoP / DPoP proofs + request headers (client side). Depends only on `pyjwt` + `cryptography`.
+
+Part of the [client-attestation-sdk](../README.md) monorepo; wire-compatible with the Java,
+TypeScript, and Go ports.
+
+## Install
+
+Not on PyPI yet. Install from a clone of this repository:
+
+```bash
+pip install -e '.[test]'
+```
+
+## Use
+
+```python
+from client_attestation_sdk import (
+    SigningKeyPair, ClientAttestationBuilder, ClientAttestationCredential,
+)
+
+# Attester issues the attestation, binding the client's public instance key
+attester = SigningKeyPair.generate("ES256")
+attestation = (
+    ClientAttestationBuilder(attester, "https://attester.example.com")
+    .client_id("https://rp.example.com")
+    .confirmation_jwk(client_instance_public_jwk)
+    .expires_in(300)
+    # optional: .authorization_details(...) / .workload(...) / .operator(sub, issuer=None) —
+    # operator names who's accountable for running the client (RFC 8693 may_act-shaped; an
+    # assertion, not proof of authorisation), distinct from client_id and from the principal.
+    .build()
+)
+
+# Client mints a fresh proof per token request
+instance = SigningKeyPair.from_jwk(my_instance_private_jwk, "ES256")
+cred = ClientAttestationCredential(attestation, instance)
+
+headers = cred.pop_headers("https://rp.example.com", "https://as.example.com")   # PoP-JWT mode
+# or
+headers = cred.dpop_headers("POST", "https://as.example.com/as/token.oauth2")    # DPoP combined mode
+# -> {"OAuth-Client-Attestation": "...", "OAuth-Client-Attestation-PoP" | "DPoP": "..."}
+```
+
+The one-call `ClientAttestation` orchestration class (see the [root README](../README.md#get-a-token-in-one-call))
+wraps this: `ClientAttestation(host, pop_method="dpop_combined")` switches it to DPoP mode, and a fetched
+challenge is carried through automatically as the PoP JWT's `challenge` claim or the DPoP proof's `nonce`
+claim, whichever mode is active.
+
+In DPoP mode the AS can issue a DPoP-bound token (`token_type: DPoP`). Use `ca.request_headers(method, url)`
+to get `Authorization: DPoP <token>` plus a fresh `DPoP` proof (with `ath` and any nonce the resource asked
+for), or `ca.requests_auth()` / `ca.httpx_auth()`, which also re-send once on a `use_dpop_nonce` challenge.
+Bearer tokens get just the `Authorization` header, as before.
+
+Other options on `ClientAttestation`:
+
+- `require_challenge=True` (default) - if the attester advertises a challenge endpoint and it fails, the flow
+  fails rather than minting without a challenge. `False` restores the old lenient behaviour.
+- `allow_insecure=False` (default) - `pf_host` and the discovered endpoints must be https, except loopback.
+- `trace=[...]` with `trace_redact=True` (default) - each wire call is recorded as a shell-quoted curl string
+  with every credential replaced by `<redacted:N bytes>`. `trace_redact=False` records them verbatim - for
+  local debugging only.
+
+`CLIENT_ATTESTATION_TOKEN_FILE` or `SPIFFE_ENDPOINT_SOCKET` set to a path that does not exist now raises
+`EvidenceNotFound` naming the variable, instead of falling through to the next evidence source.
+
+## Token validator
+
+The same distribution ships a resource-server validator (`token_validator`) — the side that *receives* and
+checks a token:
+
+```python
+from token_validator import AccessTokenValidator, ValidatorConfig
+
+validator = AccessTokenValidator(ValidatorConfig(
+    issuer="https://issuer.example.com", audiences=["https://api.example.com"],
+    jwks_uri="https://issuer.example.com/jwks", required_scopes=["read"]))
+
+result = validator.validate(access_token)          # signature + iss/exp/nbf + audience + scope
+if result.valid:
+    print(result.subject, result.scopes)
+else:
+    print(result.error)                            # e.g. "expired", "insufficient_scope"
+
+# optional RFC 7662 introspection (opaque tokens / revocation):
+result = validator.validate_active(access_token)
+```
+
+## SPIFFE workload identity → attestation bridge
+
+`client_attestation_sdk.spiffe` is a lightweight, standards-shaped stand-in for a SPIRE **agent**'s
+Workload API. It attests a workload by selector match and issues a **JWT-SVID** (`sub` = the SPIFFE ID,
+signed by the trust domain), alongside the workload's **attested attributes** — which then become the
+`workload` claim of a Client Attestation, so the AS discloses SPIFFE-attested attributes instead of static
+metadata. Maps 1:1 onto real SPIRE later; only the transport differs.
+
+```python
+from client_attestation_sdk import SpiffeAgent, SigningKeyPair, ClientAttestationBuilder, to_workload_claim
+
+agent = SpiffeAgent("banking.demo", SigningKeyPair.generate("ES256"))
+agent.register({"docker:label:app": "payment-agent"}, "payment-agent",
+               {"region": "emea", "entitlements": ["initiate_payment"]})
+
+svid = agent.fetch_jwt_svid({"docker:label:app": "payment-agent"}, audience="https://as.example.com")
+attestation = (ClientAttestationBuilder(attester, "https://attester.example.com")
+               .client_id(svid.spiffe_id).confirmation_key(instance)
+               .workload(to_workload_claim(svid))          # SPIFFE ID + attested attributes + the SVID
+               .expires_in(300).build())
+```
+
+Runnable end to end: `PYTHONPATH=src python3 examples/spiffe_bridge.py`. Verify a JWT-SVID against the
+trust bundle with `verify_jwt_svid(token, agent.trust_bundle(), audience, trust_domain)`.
+
+## Test
+
+```bash
+pip install -e .[test]
+pytest
+```

client_attestation_sdk-0.2.0/pyproject.toml

@@ -0,0 +1,57 @@
+[build-system]
+requires = ["setuptools>=77"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "client-attestation-sdk"
+version = "0.2.0"
+description = "Client-side builder SDK for OAuth Attestation-Based Client Authentication"
+readme = "README.md"
+requires-python = ">=3.10"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+authors = [{ name = "ID Partners Pty Ltd" }]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Intended Audience :: Developers",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3 :: Only",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Security",
+    "Typing :: Typed",
+]
+dependencies = [
+    "pyjwt>=2.8",
+    "cryptography>=42",
+]
+
+[project.urls]
+Homepage = "https://github.com/ID-Partners/client-attestation-sdk"
+Source = "https://github.com/ID-Partners/client-attestation-sdk/tree/main/python"
+
+[project.optional-dependencies]
+test = ["pytest>=7", "pytest-cov>=5"]
+# Optional integrations. The core never imports these at module load; each is imported only by the
+# feature that needs it.
+httpx = ["httpx>=0.24"]          # ClientAttestation.httpx_auth()
+requests = ["requests>=2.28"]    # ClientAttestation.requests_auth() is a requests auth hook
+aws = ["boto3"]                  # AwsWebIdentitySvidSource (sts:GetWebIdentityToken)
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+client_attestation_sdk = ["py.typed"]
+token_validator = ["py.typed"]
+authz_challenge = ["py.typed"]
+
+[tool.coverage.run]
+source = ["client_attestation_sdk", "token_validator", "authz_challenge"]
+
+[tool.coverage.report]
+# today's measured coverage; raise it, never lower it
+fail_under = 94

client_attestation_sdk-0.2.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

client_attestation_sdk-0.2.0/src/authz_challenge/__init__.py

@@ -0,0 +1,55 @@
+"""Agent-side handling of a policy enforcement point's AUTHORIZATION CHALLENGES.
+
+When a PEP will not let a call proceed as presented, it does not simply deny — it says what would
+make the call permissible: an authenticated user, a specific authorisation for THIS instruction, a
+verified credential, a consent, a lodged intent. This package is the client half of that
+conversation:
+
+* :func:`parse_challenge` — turn whatever the PEP said (REST status + ``WWW-Authenticate`` + body,
+  a JSON-RPC error, an MCP tool result) into one typed :class:`Challenge`. Pure; vector-pinned across
+  language ports.
+* :class:`CibaClient` — the OpenID CIBA client: raise a decoupled push to the human's authenticator
+  and poll for the answer at the AS's cadence (the pacing rules are the part everyone gets wrong).
+* :class:`CibaResolver` / :class:`WebConsentResolver` — the ceremony state machines: dedupe, channel
+  choice, push, settle, terminal record, and verification that a resumed call matches what the human
+  approved. Deployment edges (directories, device registries) are injected via :class:`Hooks`.
+
+Vocabulary is fixed in :mod:`.challenge` (challenge types) and :mod:`.resolver` (statuses,
+channels, assurance rungs the resolver may claim).
+"""
+from . import challenge as _challenge
+from . import ciba as _ciba
+from . import resolver as _resolver
+from .challenge import (
+    AUTHN, CHALLENGE_TYPES, CONSENT, IDENTITY_PROOFING, INTENT, RESOURCE_AUTHORISATION,
+    Challenge, parse_challenge, parse_www_authenticate,
+)
+from .ciba import (
+    APPROVED, CIBA_GRANT, DENIED, EXPIRED, PENDING,
+    CibaClient, CibaError, CibaRequest, ClientAuth, PrivateKeyJwtAuth,
+    private_key_jwt_assertion, urllib_http,
+)
+from .resolver import (
+    ASSURANCE_DEVICE_APPROVED, ASSURANCE_WEB_CONSENT, CHANNEL_DEVICE, CHANNEL_LOCAL, CHANNEL_WEB,
+    TERMINAL, Ceremony, CeremonyStore, ChallengeResolver, CibaResolver, Hooks, MemoryStore,
+    Pending, PollResult, ProofingResolver, Resolved, Unavailable, WebConsentResolver,
+    SUBJECT_KEY, new_code, new_handle, transaction_hash,
+)
+
+__all__ = [
+    # challenge
+    "Challenge", "parse_challenge", "parse_www_authenticate", "CHALLENGE_TYPES",
+    "AUTHN", "RESOURCE_AUTHORISATION", "CONSENT", "IDENTITY_PROOFING", "INTENT",
+    # ciba
+    "CibaClient", "CibaError", "CibaRequest", "ClientAuth", "PrivateKeyJwtAuth",
+    "private_key_jwt_assertion", "urllib_http", "CIBA_GRANT",
+    "PENDING", "APPROVED", "DENIED", "EXPIRED",
+    # resolver
+    "ChallengeResolver", "CibaResolver", "WebConsentResolver", "ProofingResolver", "Hooks",
+    "Ceremony", "CeremonyStore", "MemoryStore",
+    "Pending", "Resolved", "Unavailable", "PollResult",
+    "transaction_hash", "new_code", "new_handle", "SUBJECT_KEY", "TERMINAL",
+    "CHANNEL_DEVICE", "CHANNEL_WEB", "CHANNEL_LOCAL",
+    "ASSURANCE_DEVICE_APPROVED", "ASSURANCE_WEB_CONSENT",
+]
+__version__ = "0.2.0"