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

Record expanded portal production rollout
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source
This commit is contained in:
tegwick 2026-08-08 23:21:47 +02:00
parent 8229c6dd33
commit 6589294ae7
1 changed files with 16 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -173,3 +173,19 @@ state_hub_task_id: "05046780-9625-47c2-8caf-f57e9239c603"
When a tenant requires SAML/OIDC federation, SCIM, directory synchronization,
just-in-time provisioning, or customer-owned lifecycle, create a dedicated
cross-repository plan against the provider-neutral contracts.
## Production rollout (2026-08-08)
Commit `8229c6d` passed 115 tests with three external-provider skips, was
published as
`forgejo.coulomb.social/coulomb/user-engine@sha256:cef2fdb19fd001a9d2a64742f58dacdcf2ff5868ce50685c91eaad7880645fd0`,
and rolled out successfully on Railiance. Public health returns schema
`0001_initial`, KeyCape login returns a PKCE redirect, and `/onboarding`,
`/admin/{tenant}`, and `/platform` are recognized protected routes (403
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.