You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Activate the portal machine identity after verifier deployment #6448
Preparing the portal's separate machine credential must not enable customer Dex token issuance before the portal can reject machine identities at its browser boundary. The client-credentials grant is global, including for the existing browser client.
Outcome
Activate the prepared machine identity through a separate reviewed Git change after its strict verifier is deployed. Start with read-only portal access, then prove the real authentication boundaries without exposing credentials or tokens.
Acceptance
The preparation in feat(portal): prepare a separate machine identity #6440 is delivered through protected GitOps, with metadata-only evidence that the generated credential, durable custody and Dex projection are ready. Its production client-credentials grant remains disabled until activation.
A signed release containing the strict machine verifier and empty-connector browser refusal from business-site #665 is deployed and verified. A source merge or synthetic fixture is insufficient.
Recovery/adoption, current-main restoration, live-health, exact-head CI, review and protected deployment prerequisites are satisfied before the explicit global-grant flip. The source and deployed runtime versions are known.
The activation change enables the grant and the non-secret machine audience/subject settings with no write grants. The credential stays in native workload custody; agents never read, print, copy or transmit it or production tokens.
A reviewed native verifier obtains a token internally and proves that a live API read succeeds, an ungranted write fails, and browser/machine identities cannot cross authentication boundaries. It emits no credential, token or private response data.
Native evidence still covers both grant states, exact issuer/signature/single audience/subject, five-minute token lifetime, and refusal of refresh/offline access and machine browser redirects.
Part of #6439. That parent retains the overall live-acceptance outcome; this child owns the separate activation stage.
Activity