intyga-sdk 1.0.0__tar.gz

intyga_sdk-1.0.0/CHANGELOG.md

@@ -0,0 +1,189 @@
+# Changelog
+
+All notable changes to `intyga-sdk` (Python) are documented here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versions follow [SemVer](https://semver.org/).
+
+## [Unreleased]
+
+## [1.0.0]
+
+- Packaging: sdists include the changelog, tests and shared vectors so the source distribution can
+  run its receipt-verification tests outside the monorepo.
+
+- Verify profile-carried WebAuthn audit signatures with caller-trusted signer keys, origin and RP ID.
+  Report explicit per-event signature status and key trust; add strict signature acceptance for
+  single and bulk evidence. Audit signature checks do not replace full approval-receipt verification.
+
+- **DIV/DEWP 1.0 pre-release correction (2026-09-27 review L15-L18, I7, I8):** signed timestamps use one
+  strict RFC 3339 grammar (`datetime.fromisoformat` accepted a bare date as a naive datetime, a
+  zone-less time and a space separator). `stable_stringify` refuses a string with an unpaired
+  surrogate (`NonCanonicalValue`, DIV §4.1). A WebAuthn `topOrigin` differing from `origin` is
+  refused. `verify_platform_receipt` ignores `require_user_verification=False`. A key mapped to two
+  DIDs counts once toward a quorum. RSA-PSS anchors require a 32-byte salt and a 2048-bit modulus
+  (was `PSS.AUTO`). Divergence evidence is held to the quorum's seq-range and witness-time rules; a
+  Rekor entry establishes divergence only with submitter keys pinned. Pinned in all five languages by the `verifierInputHardening` parity vectors; no canonical bytes change for valid input.
+- **DIV 1.0 pre-release correction (H1):** `verify_approval_receipt`, `verify_delegation` and
+  `verify_agent_authority` accept `expected["requirement"]` (`{"requiredApprovals": int,
+  "requesterCannotApprove": bool, "requireHardwareKey": bool}`); export `WEAKER_REQUIREMENT_REASON`.
+  The signed `requirement` is authored by the signers, so one approver (possibly the requester) could
+  self-compose a 1-of-1 receipt for a 3-of-3 four-eyes action and it verified. A weaker signed
+  requirement is now refused before any signature is counted when the caller supplies its own rule
+  (DIV §5 step 3d), on approval, offline, delegation and agent-authority verification; the reason
+  starts "signed requirement is weaker than the relying party's policy". Omitting the floor keeps the
+  previous behaviour, which proves only the quorum the signers stated. No signed byte changes; shared
+  parity vectors pin it in all five languages.
+- **DEWP evidence verification (1.0 pre-release correction, Sep 2026):** an entry with a canonical
+  preimage reads `tenantSeq` only from it (None ⇒ no counter) and fails when its redaction counter
+  disagrees; a tenant-bound entry fails when the bundle declares no tenant; a preimage under an
+  unknown profile fails; repeated leaves/seqs and inconsistent leaf counts fail; a checkpoint with no
+  `chainHash`/`anchoredAt` is never anchored. New `verify_evidence_bundle(trusted_checkpoints=...)` and
+  `verify_bundle(trusted_checkpoint=...)` take caller-held roots-file records; a single proof counts a
+  Rekor/TSA anchor only against one. `is_well_formed_anchor` requires a registered algorithm. Pinned
+  by the shared `dewpEvidenceHardening` vectors.
+- **DIV 1.0 pre-release correction (PK-11):** under a signed `requireHardwareKey`, a WEBAUTHN witness
+  whose signed authenticatorData carries the Backup Eligible or Backup State flag no longer counts
+  toward the quorum (DIV §4.4.5 rule 6) — a relying party now catches an issuer that let a synced
+  passkey sign a hardware-pinned action. No signed byte changes; shared parity vectors pin it in all
+  five languages.
+- **Breaking (DEWP 1.0 pre-release correction):** the anchored preimage is now
+  `[dailyRoot, timestamp, issuer, algorithm, seqStart, seqEnd, chainHash]`; anchors lacking the
+  position fields never verify. External witness times (Rekor `integratedTime`, TSA `genTime`) must
+  fall within `maxAnchorLagSeconds` (default 86400) after — or 300 s before — the checkpoint's claimed
+  time; anchors must match the checkpoint's seq range, chain hash and `anchoredAt`; evidence-bundle
+  chain hashes are recomputed; verdicts expose per-issuer witness times; an optional pinned Rekor
+  submitter key is enforced. A supplied root is reported as `rootSource: "caller-supplied"` (was
+  `"independent"`).
+- A non-empty `allowedAaguids` is refused exactly like `requireHardwareKey`: bare-key witnesses do not
+  count and offline proofs are rejected (DIV §4.3.2/§5a.3).
+
+- Add opt-in RFC 3161 TimeStampToken verification through OpenSSL 3, with caller-pinned TSA
+  certificate/CA trust, explicit offline CRL or unchecked revocation, and quorum/bundle integration.
+- Scope Rekor log-key trust to one issuer for multi-issuer policies; legacy unscoped keys remain
+  accepted only when the policy trusts exactly one issuer.
+
+- Enforce DIV §5 identity trust for multi-approver quorums; preserve DIV §4.4.2 ES256
+  compatibility for absent/null/unknown witness labels, while refusing AUTO_APPROVED witnesses.
+- Validate DEWP protocol, version and declared hash/serialization/Merkle algorithms before
+  accepting proof or evidence bundles. Legacy numeric revisions 1/2 remain supported without
+  a protocol declaration. Shared cross-language fixtures cover these contracts.
+- Preserve challenge-issued agent context through approval polling for DIV continuity checks.
+- Public witness lookups require no credentials and refuse non-success HTTP responses.
+- Default HTTP transports use finite request timeouts and refuse redirects; caller-supplied
+  transports remain the caller's responsibility.
+
+- **Wire format: DIV v1 agent intents now sign `action`, `agent`, `session`, `nbf`, and `exp` instead of ordinary `expiresAt`; `div-agent-authority` requires `parentReceiptHash` (null for a root).** Older §5b seals lacking that key cannot verify under this pre-release profile and must be re-sealed. All canonical producers, five verifier ports and vectors must move together; the ordinary HUMAN/SERVICE intent keeps `expiresAt`.
+
+- **Wire format: the DIV Intent Payload gained a REQUIRED `evidence` field, and it must be `null`.**
+  `div-intent-verification` and `div-offline-intent` now carry `"evidence":null` in the signed bytes
+  (DIV §4.3.4); `div-delegation`, `div-agent-authority` and `div-platform-intent` deliberately do
+  not. `null` is signed and load-bearing, exactly as `requester.attestation`'s null is: it is the
+  payload's explicit statement that the authorization was not conditioned on any external fact.
+  Verification refuses a payload whose `evidence` key is absent, and refuses any non-`null` value
+  rather than treating it as unconditioned — the same fail-closed-on-unknown rule as the
+  `signerClass` registry, and checked before Local Payload Reconstruction so an unsupported payload
+  shape does not surface as a parameter mismatch. Absent and `null` are distinguished explicitly;
+  collapsing them would make the check a no-op. All golden vectors were regenerated.
+
+- Align cross-language receipt and audit verification: platform receipts, agent-authority seals,
+  self-certifying DID trust, single/multi-event bundles, embedded ES256 signatures, tenant sequence
+  checks, checkpoint continuity, anchor quorum and Rekor. Shared executable fixtures cover valid
+  artifacts and refusals; no wire format changes.
+- Refuse unknown witness signature algorithms. Require identity-bound trust when the signed
+  `requesterCannotApprove` rule is set; key-only trust cannot enforce requester identity.
+- **`verifyRootsChain` range-checks the FIRST entry.** The non-integer and self-inverted seq-range
+  checks were gated on having a predecessor, so the first entry was never range-checked — and a
+  single-entry `roots.jsonl` (a new tenant, or the first day after a truncation) is exactly where
+  the first entry is the only one. Such a file verified clean here while Go and Rust refused it.
+  Only the overlap check is relational now. New `single-entry-inverted-seq-range` and
+  `single-entry-non-integer-seq-range` parity vectors pin it in all five ports.
+
+- **Close approval-flow transport and argument races.** The callable guard now validates and
+  detaches one canonical-JSON snapshot before its first await, then uses that snapshot for the
+  challenge, local receipt verification, nonce consumption and execution. The wrapped function
+  therefore receives JSON types: a tuple arrives as a list and an integral float such as `1.0` as
+  the int `1`. Arguments with no portable JSON form (NaN, `-0.0`, integers outside the portable
+  range) are refused before any challenge is created. Authenticated HTTP
+  requests refuse redirects, so Basic and bearer credentials cannot be forwarded to another
+  origin. `require_approval` now derives the gateway TTL and monotonic local deadline from one
+  duration and cancels authentication/HTTP I/O when that deadline elapses. Transport
+  now uses a per-request HTTPX async client so deadline cancellation closes the connection instead
+  of leaving a blocking urllib read worker. OS DNS resolution can still outlive cancellation and
+  delay `asyncio.run()` shutdown; no hard process-shutdown bound is claimed.
+- `authorize()` now omits `actionType` when it is unset, matching the gateway's optional-field
+  schema, and the manual README flow consumes its verified nonce before executing.
+- **Tokens are re-exchanged before they expire, and once more on a 401.** `IntygaClient` cached
+  the first `client_credentials` exchange for the life of the process and never read `expires_in`,
+  so a long-lived service (the `require_human_approval` guard holds one client) or a long
+  `require_approval` poll died at the gateway's TTL with a bare `GatewayRefused(401)` and stayed
+  dead until restart. The client now honours `expires_in` on a monotonic clock — the cache is served
+  only while more than `min(60 s, expires_in / 10)` of it remains, then exchanged again — and a 401
+  against a token it exchanged itself clears the cache and retries exactly once (clock skew, a
+  gateway-side TTL change). An explicit `token` is never retried: it has nothing to re-exchange
+  with. An absent or non-numeric `expires_in` keeps the old cache-until-401 behaviour. This is what
+  lets the gateway shorten agent/human token lifetimes.
+- **A stored `intyga login` credential says how to fix itself.** It cannot be refreshed (no
+  secret), so its JWT `exp` is now read — unverified, a hint for the message only — and an expired
+  one, or a 401 the gateway returns for it, raises `GatewayRefused(401)` telling you to run
+  `intyga login` again instead of surfacing the raw rejection; the cache is cleared so a fresh
+  login is picked up on the next call.
+- **`require_human_approval` can now verify the receipt (DIV §5).** It decided on the gateway's
+  `status` string alone: it never read `receipt`, never checked a signature, and never redeemed the
+  nonce — so the gateway's word was the only thing between an agent and an irreversible action, in
+  the SDK's only action-executing path. Pass `approvers` (plus `expected_origin` / `expected_rp_id`
+  for a passkey witness) and the guard re-derives the canonical payload from the target and kwargs
+  it is about to execute, verifies the signatures against YOUR keys, refuses a result carrying no
+  receipt, and consumes the nonce before calling the function. Omitting `approvers` keeps the old
+  behavior for compatibility and now warns at decoration time instead of being silent about it.
+- **Refuse an omitted `expected['actionType']` or `expected['params']` (DIV §4.4.1).** Both
+  defaulted to `""`/`{}`, so a caller who omitted or misspelled either key — easy in an untyped
+  dict API — rebuilt a payload bound to nothing and got `ok: True` against a receipt minted with
+  those same empty values. An explicitly written `""`/`{}` is still accepted; only omission is
+  refused. Applies to `verify_delegation` as well.
+- **DEWP root selection now mirrors the TypeScript reference's fallback chain.** Only
+  `anchor.dailyRoot` was read, but the reference producer omits `anchor` entirely until signed
+  anchors exist — so the ordinary console export reported `INVALID`, the verdict that reads as
+  tampering, for an untampered bundle. `legacyAnchor.dailyRoot` and `proof.checkpointRoot` are now
+  read after it, still as `rootSource: "self-asserted"` and still not `ok`.
+- **A redacted, commitment-only bundle is `ok` again at `COMMITMENT_VERIFIED` (DEWP §15).** `ok`
+  required a leaf binding, which an export carrying no preimage cannot supply by design. A
+  prover-supplied unknown `profile` over content the bundle DID ship still disqualifies.
+- **`verify_inclusion_proof` returns `False` for a malformed proof** instead of raising `KeyError`
+  — it is a documented predicate, and only `verify_bundle`'s try/except was hiding that.
+- **`verify_anchor_signature` accepts base64url** for the trusted key and the anchor signature,
+  matching `@intyga/verify`. `base64.b64decode` without `validate` silently discards `-` and `_`,
+  so a base64url anchor decoded to different bytes and read as an invalid signature (DEWP §5.2).
+- **An `int` above the double range is a `NonCanonicalValue` refusal, not an `OverflowError`,**
+  out of `stable_stringify` / the canonical payload builders.
+- Build-system pin raised to `setuptools>=77.0.0` — the PEP 639 `license` / `license-files`
+  metadata this project declares cannot be built by anything older.
+- **Refuse a forward-dated offline proof or delegation (DIV §5a.3 rule 3, §5a.6 step 1).** The
+  window caps bounded a proof's WIDTH but never its POSITION, so a quorum-signed proof dated years
+  ahead with a compliant 60-minute (or 72-hour) window verified today and kept verifying until that
+  date. The check is unconditional — the audit/`allow_expired` override re-examines a proof that was
+  valid and has lapsed, and does not reach one dated in the future.
+- **Refuse a signed `requirement.requiredApprovals` below 1 (DIV §4.3.2).** §5 step 7's "at least
+  `requiredApprovals`" is satisfied vacuously by 0, so the minimum is now enforced explicitly
+  instead of by an undocumented floor.
+- `require_human_approval` (`intyga_sdk.guard`) — gate any sync/async callable behind a signed
+  human approval; the integration surface for LangChain / CrewAI style frameworks (they consume
+  plain callables). Positional arguments are refused so every signed parameter is named.
+- Typed exceptions (`intyga_sdk.errors`): `IntygaError`, `GatewayRefused` (with `.status`),
+  `GatewayUnreachable`, `ApprovalRefused` — replacing bare `Exception` raises. All subclass
+  `Exception`, so existing handlers keep working.
+- `require_approval()` now merges the challenge `nonce` into every result (terminal and EXPIRED),
+  matching the TS/Go/Rust ports — previously the one-shot helper's caller could not feed
+  `verify_approval_receipt` or record redemption.
+- PEP 561 `py.typed` marker shipped.
+
+- **Security (I11):** `IntygaClient` raises `ValueError` for a `gateway_url` that is not `https://`,
+  except `http://` to a loopback host (`localhost`, `127.0.0.0/8`, `::1`) for local development.
+
+
+Initial public release.
+
+- Async client: `authorize` / `status` / `consume` / `require_approval`; `target` is required
+  (DIV Target Isolation).
+- DIV canonical payloads and `verify_approval_receipt` against a caller-supplied trust anchor.
+- DEWP Core primitives (§9.1) plus single-bundle verification. Deliberate, documented limits:
+  `signature_verified` and `anchor_verified` are always `False` here, and the §5.4 checkpoint
+  chain is TypeScript-only — see the README's "DEWP conformance" section.

intyga_sdk-1.0.0/LICENSE

@@ -0,0 +1,201 @@
+                                 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 2026 Janbjer Technologies AB
+
+   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.

intyga_sdk-1.0.0/MANIFEST.in

@@ -0,0 +1,3 @@
+include LICENSE README.md CHANGELOG.md
+recursive-include tests *.py
+recursive-include vectors *.json