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
Preserve client sign-in while moving between the website and portal #652
Clients need a clear way back to the public website from both their workspace and the sign-in form. Returning to the portal should reuse a valid session without another credential prompt, while invitations, current membership, expiry and explicit sign-out remain enforced.
Follow-up to #649, requested by the maintainer for the public English and Danish journeys.
Acceptance:
Portal navigation returns to the corresponding public language without signing out.
The upstream sign-in form offers a clearly labeled native website link through its declarative owner.
Returning with a valid portal session opens the workspace immediately; a fresh authorization can reuse a valid identity-provider session.
Cookies contain only an opaque session reference, remain bounded by server and token expiry, and cannot restore expired, revoked or signed-out access.
Behavioral tests cover return navigation, session reuse and security boundaries; delivery includes reviewed source, publication and actual deployed readback.
#603 - feat(portal): serve the portal at the root of portal.devantler.tech [merged] #555 - feat(portal): serve devantler.tech and portal.devantler.tech from one runtime [merged]
📝 Issue Planner
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
Source delivery: #653 merged through the normal protected path as signed 7ec2d403e3adeccd00cb0d9cdc8a679affa48390. Its final PR head had green CI and an exact-head CodeRabbit review with no actionable findings. The merged result also includes the independently delivered capability settings from #651; the navigation/session implementation, privacy wording and presentation references are byte-identical to the reviewed #653 head. Original main CI is 43901170001, still in progress at this handoff.
The upstream form source is prepared and independently reviewed in devantler-tech/platform#6437 at 1bbed98e831d721ad3b8744860c3c4c6500b95d2, with all 47 CI checks green and clean Codex review. An isolated native ZITADEL 4.20.3 instance verified the real footer on desktop/mobile and the website opening in a second tab while the original login form remained open. Actual customer sign-in/SSO was not performed in that smoke.
Live acceptance is still blocked: public English/Danish pages both return HTTP 200 but still lack the new portal links; the platform recovery #6433 remains open, reached through the native dependency on devantler-tech/platform#6436. The runtime publication switch remains false. No production account, policy, session lifetime or deployment was changed by this task.
Resume after the recovery owner clears #6433: require original-main CI success, include this source in the coordinated signed release, deploy the login-form policy through its owner, and verify both public languages → portal → website → portal with a permitted invited account, followed by explicit sign-out and expiry/revocation refusal. Keep this issue open until that deployed path passes. Event-driven recheck on recovery/deployment completion; next bounded status check 2026-11-17.
Activity
coderabbitai commentedon Nov 16, 2026
🔗 Related PRs
#603 - feat(portal): serve the portal at the root of portal.devantler.tech [merged]
#555 - feat(portal): serve devantler.tech and portal.devantler.tech from one runtime [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
chore: agent-claim #652 nonce=0dc064f66889dda9cbc50efa22c19b8c
devantler commentedon Nov 16, 2026
Source delivery: #653 merged through the normal protected path as signed
7ec2d403e3adeccd00cb0d9cdc8a679affa48390. Its final PR head had green CI and an exact-head CodeRabbit review with no actionable findings. The merged result also includes the independently delivered capability settings from #651; the navigation/session implementation, privacy wording and presentation references are byte-identical to the reviewed #653 head. Original main CI is 43901170001, still in progress at this handoff.The upstream form source is prepared and independently reviewed in devantler-tech/platform#6437 at
1bbed98e831d721ad3b8744860c3c4c6500b95d2, with all 47 CI checks green and clean Codex review. An isolated native ZITADEL 4.20.3 instance verified the real footer on desktop/mobile and the website opening in a second tab while the original login form remained open. Actual customer sign-in/SSO was not performed in that smoke.Live acceptance is still blocked: public English/Danish pages both return HTTP 200 but still lack the new portal links; the platform recovery #6433 remains open, reached through the native dependency on devantler-tech/platform#6436. The runtime publication switch remains false. No production account, policy, session lifetime or deployment was changed by this task.
Resume after the recovery owner clears #6433: require original-main CI success, include this source in the coordinated signed release, deploy the login-form policy through its owner, and verify both public languages → portal → website → portal with a permitted invited account, followed by explicit sign-out and expiry/revocation refusal. Keep this issue open until that deployed path passes. Event-driven recheck on recovery/deployment completion; next bounded status check 2026-11-17.