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

docs: record native user setup and product handoff requirements
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a07ff8-19d0-7820-b4d0-1353833cb7fc
This commit is contained in:
tegwick 2026-09-12 01:08:33 +02:00
parent effd0a3170
commit 02c29eec53
3 changed files with 45 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

26
docs/vergabe-demo-company-binding.md
View file

@ -1,13 +1,13 @@
# Vergabe demo-company deployment binding
Prepared 2026-09-11 under RAPPS-WP-0014-T02 and VERGABE-WP-0019-T03/T04.
Native tenant creation is verified; application placement and onboarding remain pending.
Native tenant, user and password setup are verified; application placement and product onboarding remain pending.
| Item | Binding / execution status |
| --- | --- |
| Tenant | `tenant:trial:demo-company`; display `demo-company`; active, version 1; native operator create/readback verified |
| Purpose / data | New demo workspace; synthetic data only; no existing data import |
| Initial accounts | `demo-user1`, `demo-user2`, ordinary members; creation and private credential setup pending |
| Initial accounts | Three native memberships; one linked identity with operator-confirmed password setup. Remaining identities, actual login-name mapping and product accounts still require verification |
| Operator / acceptance | Bernd Worsch via authenticated existing operator path |
| Cluster | Railiance01, kube-system UID `a553c742-0115-43d4-99a4-a5ca56fe0786` |
| Proposed namespace | `vergabe-demo-company`; create separately from historical installations |
@ -40,8 +40,10 @@ administrator with invited status. A subsequent Create login failed with an
LLDAP service-login 401. The operator completed NK-WP-0036-T04's attended
credential-reference repair: provider and consumer login now pass, independently
verified with a directory read; the provider password and image are unchanged.
Retry native Create login for the existing intended user and verify password
setup. No directory identity is inferred from the user-domain record.
The operator confirms successful user password setup on 2026-09-12. Independent
read-only User Engine evidence shows three memberships and one linked identity.
USER-WP-0025 also delivered operator navigation, logout and tenant-name selection.
Remaining identity and product access are verified separately.
Create two ordinary memberships through User Engine. Confirm how the identity
provisioner assigns login names before provisioning the requested demo names;
@ -75,3 +77,19 @@ Validation on 2026-09-11: Helm lint passed. Rendering the proposed values
produced the pinned digest, one Recreate replica, 60m CPU request, matching
Django/probe hosts, and two distinct retained PVCs. This is local manifest
verification; it is not native deployment or tenant-creation evidence.
The next product handoff is VERGABE-WP-0019-T06: preserve the invited tenant and
recipient through an allow-listed password-setup return and land on the admitted
demo-company welcome/sign-in path. Product authentication must validate its own
NetKingdom identity and tenant; it must not reuse the operator's portal session
or silently grant staff privileges. No application SSO is implemented yet.
Latest DNS evidence, 2026-09-12: both the recursive resolver and authoritative
ns1047.ui-dns.biz return NXDOMAIN for the product hostname (A and AAAA queried
recursively). This supersedes the earlier 80.158.43.29 observation for current
execution. The zone is served by IONOS ui-dns nameservers. The operator was asked
to add only A vergabe-teilnahme.coulomb.social → 92.205.62.239, TTL 300 or default.
No DNS credentials were requested or retrieved; native record readback and TLS
remain pending. Tenant paths continue sharing this one product hostname.

14
docs/vergabe-teilnahme-pilot.md
View file

@ -9,8 +9,8 @@ the historical deployment is still live.
Before native admission, record the following non-secret values in the company
binding. The user selects a fresh `demo-company` workspace; see
[its prepared binding](vergabe-demo-company-binding.md). Native tenant creation
and hostname admission are pending; example values do not create a tenant.
[its prepared binding](vergabe-demo-company-binding.md). Native tenant/user/password setup is verified; application hostname admission
and product placement remain pending.
| Binding | Required evidence |
| --- | --- |
@ -150,3 +150,13 @@ NK-WP-0036-T04. Tenant-path application source 9345a1b passes 98 tests and seven
local browser checks; image publication 44 passed with digest
sha256:cebe8ca6218cc89f903e8a69e06ac50d3812526d4119cf4da485cc173f674b68.
Live edge/data admission remains open. See the updated demo-company binding for execution status.
2026-09-12 update: directory credential reconciliation succeeded, the operator
confirmed portal login/logout and user password setup, and live records show
three demo-company memberships with one linked identity. Native provisioning
is no longer the current blocker. The product still needs DNS/TLS, fresh data
custody, placement and recovery. VERGABE-WP-0019-T06 now explicitly tracks the
requested tenant welcome and connection to the new NetKingdom identity. The
earlier manually provisioned Django account path remains an interim capability;
it does not make the directory password a product credential or implement SSO.