Files
zeekayandHanzo Dev b30092fce9 iam: a certificate is read from the partition its application lives in
GetApplication resolved admin/<app>. GetCert resolved <IAM_ORG>/<cert>. An
application's `cert` field is a bare name and the cert row is written owner=admin,
so any deployment whose IAM_ORG was not "admin" — which is every real one — read
its application fine and then could not find that application's certificate.

The store had the cert the whole time. Only the question was addressed to the
wrong tenant, and IAM answered it the way it answers any miss: "the entity does
not exist". So the failure named a missing certificate rather than a misaddressed
lookup, and what actually broke was one step further on — with no cert there is no
key to validate a bearer against, so the process cannot authenticate anything.

Seen on hanzo-devnet the moment identity moved in-process: /v1/models 503,
`read cert "cert-hanzo" for application "hanzo-cloud": the entity does not exist`,
while get-cert?id=admin%2Fcert-hanzo returned that same cert with a 200.

The partition is now named once — PlatformOwner — and applications, organizations
and certs all read through it, so an application and its own certificate can no
longer be looked up in two different places.

Asserted on the REQUEST URL, not on a response: the defect was never in what IAM
returned, it was in which tenant we asked. Mutation-checked — putting GetCert back
on c.OrganizationName fails the test.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-02 15:35:38 -07:00
..