aegis-knox3-extension is a thin Knox service that reads the Subject established by Knox’s provider
chain and hands MCP requests to the shared Aegis governance plane. It compiles against the released
Knox 3.0.0 public API in provided scope, which uses javax.servlet 4.0.1 and javax.ws.rs 2.0.
At the Knox trunk snapshot inspected on 2026-10-03, 3.1.0-SNAPSHOT had moved to the Jakarta
namespace: its root pom.xml set jakarta.servlet-api 6.0.0, jakarta.ws.rs-api 3.1.0, and Jersey
3.1.12. That snapshot also carried KnoxIDF identity work, including RFC 8693 token-exchange constants
in gateway-util-common (KnoxIDFConstants) and the JWT federation provider
(JWTFederationFilter). These are historical upstream observations from the 2026-10-03 design
snapshot, not claims about current Knox trunk.
A javax-built extension does not load in a Jakarta container. Aligning Aegis delegated identity with KnoxIDF and running on Knox 3.0.0 javax are therefore two different Knox lines.
JerseyServiceDeploymentContributorBase, SubjectUtils, principals) and the real Knox 3.0.0
AclsAuthorizationFilter. Servlet request and context objects were supplied by the test; no servlet
container or Jersey runtime was booted by the default build.-Preal-engines with AEGIS_KNOX_HOME pointing at an unpacked Knox
3.0.0, installed the knox-bundle jar into Knox ext/, wrote a topology, started the Knox gateway
process, and drove MCP calls through it. Retained run files are under examples/adopters/, but they
are not candidate-bound evidence for the current dirty tree.docs/evidence/knox-3.0.0-cold-install/ used an earlier
four-jar layout and is incomplete historical recorded-unattested evidence.aegis-knox3-extension on Knox 3.0.0 javax as the released-Knox proof point. Claim only what
candidate-bound evidence shows.Gateway.aegis-config gateway build.