aac-invoke-auth 0.1.0__tar.gz

aac_invoke_auth-0.1.0/LICENSE

@@ -0,0 +1,177 @@
+
+                                 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

aac_invoke_auth-0.1.0/PKG-INFO

@@ -0,0 +1,147 @@
+Metadata-Version: 2.4
+Name: aac-invoke-auth
+Version: 0.1.0
+Summary: AAC sidecar-to-agent invoke-push authentication (AAC1-HMAC-SHA256) — signing and verification core, with FastAPI mounting surfaces.
+Author: Agent Authority Cloud Project
+License-Expression: Apache-2.0
+Keywords: aac,agent,authorization,hmac,middleware,fastapi,sidecar
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+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: Framework :: FastAPI
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: fastapi
+Requires-Dist: fastapi>=0.115; extra == "fastapi"
+Provides-Extra: test
+Requires-Dist: pytest>=8.0; extra == "test"
+Requires-Dist: fastapi>=0.115; extra == "test"
+Requires-Dist: httpx>=0.28; extra == "test"
+Dynamic: license-file
+
+# aac-invoke-auth
+
+Authenticate `/invoke` pushes from your paired AAC sidecar.
+
+When your agent runs behind an AAC sidecar, the sidecar verifies the
+cross-organizational authority chain and then POSTs the verified context
+to your agent's `/invoke` endpoint. The `X-AAC-*` headers on that push
+are your agent's **entire view** of the verified chain — so your agent
+must be able to tell a genuine sidecar push from a forged one. This
+package is that check: the sidecar HMAC-signs every push with a pairing
+secret shared with exactly one agent, and your agent verifies the
+signature before trusting anything.
+
+The verification core is standard-library only (`hmac`, `hashlib`) and
+framework-agnostic. FastAPI mounting surfaces ship behind an extra:
+
+```bash
+pip install aac-invoke-auth[fastapi]
+```
+
+## Quick start (FastAPI)
+
+Generate the pairing secret once and share the file with your sidecar
+(the sidecar's `sidecar.agent_invoke_auth.secret_file` points at the
+same file; one secret per sidecar–agent pair, never shared across
+pairs):
+
+```bash
+openssl rand -hex 32 > /etc/aac/invoke-auth/invoke-auth.secret
+```
+
+Point your agent at it and mount the middleware:
+
+```bash
+export AAC_INVOKE_AUTH_SECRET_FILE=/etc/aac/invoke-auth/invoke-auth.secret
+```
+
+```python
+from fastapi import FastAPI
+from aac_invoke_auth.fastapi import InvokeAuthGuard, InvokeAuthMiddleware
+
+app = FastAPI()
+app.add_middleware(
+    InvokeAuthMiddleware,
+    guard=InvokeAuthGuard.from_env(),
+    protected_paths=("/invoke",),   # required, exact-match
+)
+```
+
+That's the whole integration. Unsigned, tampered, replayed-stale, or
+wrong-secret pushes get a `401` with a generic detail and never reach
+your business logic; your handlers read `request.json()` unchanged.
+
+Prefer route-scoped protection? The guard is also a plain FastAPI
+dependency:
+
+```python
+from fastapi import Depends
+
+guard = InvokeAuthGuard.from_env()
+
+@app.post("/invoke", dependencies=[Depends(guard)])
+async def invoke(request: Request): ...
+```
+
+Both surfaces call the same verifier — pick whichever fits your app.
+
+## Fail-fast startup, by design
+
+`InvokeAuthGuard.from_env()` **refuses to start** when
+`AAC_INVOKE_AUTH_SECRET_FILE` is unset. A missing secret is a security
+downgrade; it should fail your deployment loudly at boot, not degrade
+into a log line nobody reads.
+
+The single escape hatch — for extraordinary cases only, such as tenant
+test/pilot environments or debugging a suspected signing mismatch — is
+setting
+
+```bash
+export AAC_INVOKE_AUTH_ALLOW_UNAUTHENTICATED=true
+```
+
+explicitly (only the exact value `true`; a typo still fails the boot).
+An opted-out agent accepts every push unverified and logs a prominent
+warning at startup so the posture is visible in your logs. Never run
+this in production: the sidecar side has a symmetric `dev_mode`
+interlock, and both exist to make "unauthenticated" impossible to reach
+by accident.
+
+## Testing your agent
+
+`aac_invoke_auth.testing` ships with the package:
+
+```python
+from aac_invoke_auth.testing import signing_test_client
+
+client = signing_test_client(app)          # wraps FastAPI's TestClient
+response = client.post("/invoke", headers=aac_headers, json=payload)
+```
+
+`post()` calls to protected paths are signed exactly the way the paired
+sidecar signs them (secret read from `AAC_INVOKE_AUTH_SECRET_FILE`);
+everything else passes through. So your test suite exercises the real
+production verification path instead of opting out of it.
+
+## Wire format
+
+`AAC1-HMAC-SHA256` over method, path, timestamp, a SHA-256 body digest,
+and every `X-AAC-*` header (derived by rule, so header
+insertion/removal after signing fails verification). Freshness window
+±30s. The normative canonicalization text lives in the AAC Engineering
+Specification §III.2.4a; frozen known-answer vectors live in this
+package's test suite — a change that breaks a vector is a wire-format
+break, not a refactor.
+
+Ports of this middleware for other stacks (Express, Spring, Go
+net/http) follow the same model; the core stays standard-library-only
+in every language precisely to keep those ports mechanical.

aac_invoke_auth-0.1.0/README.md

@@ -0,0 +1,118 @@
+# aac-invoke-auth
+
+Authenticate `/invoke` pushes from your paired AAC sidecar.
+
+When your agent runs behind an AAC sidecar, the sidecar verifies the
+cross-organizational authority chain and then POSTs the verified context
+to your agent's `/invoke` endpoint. The `X-AAC-*` headers on that push
+are your agent's **entire view** of the verified chain — so your agent
+must be able to tell a genuine sidecar push from a forged one. This
+package is that check: the sidecar HMAC-signs every push with a pairing
+secret shared with exactly one agent, and your agent verifies the
+signature before trusting anything.
+
+The verification core is standard-library only (`hmac`, `hashlib`) and
+framework-agnostic. FastAPI mounting surfaces ship behind an extra:
+
+```bash
+pip install aac-invoke-auth[fastapi]
+```
+
+## Quick start (FastAPI)
+
+Generate the pairing secret once and share the file with your sidecar
+(the sidecar's `sidecar.agent_invoke_auth.secret_file` points at the
+same file; one secret per sidecar–agent pair, never shared across
+pairs):
+
+```bash
+openssl rand -hex 32 > /etc/aac/invoke-auth/invoke-auth.secret
+```
+
+Point your agent at it and mount the middleware:
+
+```bash
+export AAC_INVOKE_AUTH_SECRET_FILE=/etc/aac/invoke-auth/invoke-auth.secret
+```
+
+```python
+from fastapi import FastAPI
+from aac_invoke_auth.fastapi import InvokeAuthGuard, InvokeAuthMiddleware
+
+app = FastAPI()
+app.add_middleware(
+    InvokeAuthMiddleware,
+    guard=InvokeAuthGuard.from_env(),
+    protected_paths=("/invoke",),   # required, exact-match
+)
+```
+
+That's the whole integration. Unsigned, tampered, replayed-stale, or
+wrong-secret pushes get a `401` with a generic detail and never reach
+your business logic; your handlers read `request.json()` unchanged.
+
+Prefer route-scoped protection? The guard is also a plain FastAPI
+dependency:
+
+```python
+from fastapi import Depends
+
+guard = InvokeAuthGuard.from_env()
+
+@app.post("/invoke", dependencies=[Depends(guard)])
+async def invoke(request: Request): ...
+```
+
+Both surfaces call the same verifier — pick whichever fits your app.
+
+## Fail-fast startup, by design
+
+`InvokeAuthGuard.from_env()` **refuses to start** when
+`AAC_INVOKE_AUTH_SECRET_FILE` is unset. A missing secret is a security
+downgrade; it should fail your deployment loudly at boot, not degrade
+into a log line nobody reads.
+
+The single escape hatch — for extraordinary cases only, such as tenant
+test/pilot environments or debugging a suspected signing mismatch — is
+setting
+
+```bash
+export AAC_INVOKE_AUTH_ALLOW_UNAUTHENTICATED=true
+```
+
+explicitly (only the exact value `true`; a typo still fails the boot).
+An opted-out agent accepts every push unverified and logs a prominent
+warning at startup so the posture is visible in your logs. Never run
+this in production: the sidecar side has a symmetric `dev_mode`
+interlock, and both exist to make "unauthenticated" impossible to reach
+by accident.
+
+## Testing your agent
+
+`aac_invoke_auth.testing` ships with the package:
+
+```python
+from aac_invoke_auth.testing import signing_test_client
+
+client = signing_test_client(app)          # wraps FastAPI's TestClient
+response = client.post("/invoke", headers=aac_headers, json=payload)
+```
+
+`post()` calls to protected paths are signed exactly the way the paired
+sidecar signs them (secret read from `AAC_INVOKE_AUTH_SECRET_FILE`);
+everything else passes through. So your test suite exercises the real
+production verification path instead of opting out of it.
+
+## Wire format
+
+`AAC1-HMAC-SHA256` over method, path, timestamp, a SHA-256 body digest,
+and every `X-AAC-*` header (derived by rule, so header
+insertion/removal after signing fails verification). Freshness window
+±30s. The normative canonicalization text lives in the AAC Engineering
+Specification §III.2.4a; frozen known-answer vectors live in this
+package's test suite — a change that breaks a vector is a wire-format
+break, not a refactor.
+
+Ports of this middleware for other stacks (Express, Spring, Go
+net/http) follow the same model; the core stays standard-library-only
+in every language precisely to keep those ports mechanical.