docs: apply CLAUDE-FACTS to CLAUDE.md, fix AlarmAck LDAP wording, retitle KNOWN LIMITATION 2 (#624)

Claude-Session: https://claude.ai/code/session_01Ef2ozxS7QPanGT8uoATbTe
This commit is contained in:
Joseph Doherty
2026-10-08 08:19:30 -04:00
parent 2befe9f9ba
commit 0a5d03da95
2 changed files with 93 additions and 30 deletions
+5 -3
View File
@@ -104,9 +104,11 @@
# mesh gRPC call on a login-enabled admin node) survived seven phases of prior live gates. To drive
# this rig production-faithfully:
# OTOPCUA_DISABLE_LOGIN=false docker compose -f docker-dev/docker-compose.yml up -d central-1 central-2
# Sign in as `alice` / `password` (or `bob`) against the shared GLAuth (10.100.0.35:3893,
# dc=zb,dc=local) — the same LDAP users every other node in this file already authenticates OPC UA
# sessions against. Restore the default with `docker compose ... up -d central-1 central-2` (no env
# Sign in as `admin` / `password` (OtOpcUa-Admins, AdminUI Administrator) or `multi-role` / `password`
# (member of every group) against the shared GLAuth (10.100.0.35:3893, dc=zb,dc=local). The old
# `alice`/`bob` users no longer exist there. NOTE: the serviceaccount bind password below is the
# pre-rotation value (rotated out-of-band, SEC-36, scadaproj/infra/glauth/config.toml); a real-login run
# needs the current one supplied via the environment. The data plane no longer uses LDAP at all (API keys). Restore the default with `docker compose ... up -d central-1 central-2` (no env
# var). See docs/security.md "Mesh gRPC ingress is AllowAnonymous by design" for what this actually
# exercises.
#