coulomb/user-engine
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Record tenant and authorization rollout
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source
This commit is contained in:
tegwick 2026-08-09 02:23:11 +02:00
parent 3bb73b013e
commit fafa4d708a
1 changed files with 8 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

12
workplans/USER-WP-0021-portal-product-expansion.md
View file

@ -185,7 +185,11 @@ and rolled out successfully on Railiance. Public health returns schema
without a session, rather than 404). The rollout replaces in-memory OIDC
sessions, so existing browsers must authenticate again.
The tenant authority is not currently deployed in the cluster. Platform
tenant creation therefore remains fail-closed behind the implemented optional
`TenantManagementPort`; this is part of the remaining T01 tenant-management
integration rather than a hidden local tenant registry.
2026-08-09 production follow-up: tenant-engine and its dedicated flex-auth
policy service are deployed with persistent storage and least-privilege
networking. The portal adapter created a tenant successfully and the record
survived a tenant-engine restart. The separate user-engine flex-auth policy is
also deployed and has live self-service-allow/cross-tenant-deny evidence, but
the portal runtime switch remains gated on approved event and mail receivers.
T01 remains open only for broader tenant update/retirement operations and the
final outbox transport activation.