user-engine/workplans/USER-WP-0027-account-journey-clarity.md
tegwick 62d6f8b0c7
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 2s
Record and pin verified account journey release
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a092fe-13b1-7f12-ac74-7d258af4d79c
2026-09-13 12:29:43 +02:00

113 lines
4.5 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
id: USER-WP-0027
type: workplan
title: "Clear account state and complete user, tenant-admin and platform-admin journeys"
domain: communication
repo: user-engine
status: active
owner: codex
topic_slug: communication
created: "2026-09-13"
updated: "2026-09-13"
state_hub_workstream_id: "455300ca-ec1e-569e-a584-a8dcda2595cf"
---
## Establish role-based success, failure and recovery acceptance
```task
id: USER-WP-0027-T01
status: done
priority: high
state_hub_task_id: "7f184a7c-2b93-5e6a-a15c-6fd8f3e9ff33"
```
Defined 29 journeys in docs/account-journeys.md: 13 user, 8 tenant administrator,
8 platform administrator. Each has success, failure/recovery and current support
status. The document is the browser acceptance contract, not proof all journeys
are implemented. Includes OTP state contract and cross-role/isolation checks.
## Make account controls and browser recovery reflect verified state
```task
id: USER-WP-0027-T02
status: done
priority: high
state_hub_task_id: "897988e5-32a5-55e0-a49f-92d0e39971b6"
```
Signed-out/expired sessions show Sign in; verified sessions show identity and
Log out. Logout uses existing scope confirmation; wrong shared-identity recovery
stays accessible without implying a portal session. Signed-in registration routes
to account. Browser errors retain status and gain safe recovery navigation; APIs
remain JSON. Public /security explains OTP setup/recovery without claiming factor
state or activation. Fixed HTTPS provider handoff is configurable but disabled by
default pending provider verification. `make test`: 188 tests, 3 optional skips;
layer conformance passed. `git diff --check` passed.
## Publish and verify the portal UI cleanup
```task
id: USER-WP-0027-T03
status: done
priority: high
state_hub_task_id: "90284878-ace3-5b90-96ed-845bc69f6e61"
```
Publish reviewed source, pin the CI image in rapp-user-engine, deploy with CAS,
verify readiness, signed-out browser controls, and recovery/security navigation.
Keep live OTP handoff disabled until T04 dependencies are met.
Deployed source a9ff77d, image sha256:558e489f0b6e0b7160ab0d370560a66497e12488b95531bbccca122b46331a6f, runtime pin commit 367bb1b. Deployment Ready 1/1. Eight live HTTP checks and twelve isolated Chromium checks passed; see docs/evidence/2026-09-13-account-clarity.md. No authenticated OTP acceptance is inferred.
## Complete provider OTP activation and recovery path
```task
id: USER-WP-0027-T04
status: wait
priority: high
state_hub_task_id: "9657abcb-690e-5323-8ff3-58253298ce7b"
```
Depends on KEY-WP-0035-T02/T03 and NK-WP-0033 custody handoff. Current owner route
net-kingdom-privacyidea-admin-token remains non-resolvable. Restore scoped factor
lookup and verify possession-confirmed enrollment, cancellation, replacement,
recovery and fresh login; resolve privileged portal policy. Only then configure
USER_ENGINE_MFA_MANAGEMENT_URL and accept U05U08/P04P06. Do not fake a status from
assurance claims, redirect return parameters or manual step completion.
## Close tenant and platform administrator usability gaps
```task
id: USER-WP-0027-T05
status: progress
priority: high
state_hub_task_id: "92906113-e28b-58d3-95a7-779e815d1ced"
```
Implement remaining T02T08/P02/P04/P07/P08 browser gaps from docs/account-journeys.md:
clear login-name versus display-name and lifecycle states, delivery confirmation,
consolidated onboarding diagnosis, scoped lifecycle confirmation/readback, admin
succession guard review and safe audit/support recovery. Existing headless routes
are starting points, not browser acceptance. Split into owner workplans as needed.
## Validate all journeys across roles and applications
```task
id: USER-WP-0027-T06
status: progress
priority: high
state_hub_task_id: "550886ca-f916-5637-9639-b4134b0da939"
```
Execute success/failure/recovery matrix with synthetic user, tenant admin,
platform operator, expired and wrong-tenant identities. Include invitation/mail,
actual OTP, shared sign-out, keyboard/mobile, form preservation, and authoritative
application access (USER-WP-0026-T03). Preserve VERGABE-WP-0019 real-user acceptance.
Record live evidence and hand off any residuals as live work before closing.
Implementation is split into USER-WP-0028 (user), USER-WP-0029 (tenant admin),
USER-WP-0030 (platform admin), and USER-WP-0031 (automated acceptance). These
are live workplans, not residuals parked only in the journey document.
Implemented admin journeys and automated suites are deployed; see docs/evidence/2026-09-13-journey-release.md and its machine-readable report. Full acceptance remains incomplete for the named integration/provider gaps.