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
Record the certificate-principal invariant in security/DESIGN.md #4126
#4069 adds an invariant: every place a verified client certificate selects the principal (security/auth.ts for HTTPS and WSS, server/mqtt.ts for MQTT over TLS) must install certificatePrincipal(user, getUser). The mark it sets holds the certificate admission, and every view that replaces such a principal must carry it: a recheck's cloneUserView(fresh, undefined, admission) and an MCP refresh's withCertificateAdmission. A path that does not fails closed, and its clients' live subscriptions then need a role. The live-subscription role latch (latchRoleRequirement) is keyed on that admission.
Resolution
#4280 brought security/DESIGN.md under its budget, so #4069 now records the invariant there: a subsection of the user-lookup notes ("A certificate's principal keeps one admission across its views"). The scoped-token rehydration rule names carrying a certificate admission, and server/DESIGN.md's recheck note points to the subsection. This issue closes when #4069 merges.
Activity