diff --git a/docs/plans/2026-11-15-nam-ldap-cutover.md b/docs/plans/2026-11-15-nam-ldap-cutover.md index eebbd67..3b6f003 100644 --- a/docs/plans/2026-11-15-nam-ldap-cutover.md +++ b/docs/plans/2026-11-15-nam-ldap-cutover.md @@ -7,6 +7,112 @@ > (§10 lists what changed). The independent review of 2026-11-15 is applied (§11). **Written 2026-11-15. Status: PLAN ONLY. Nothing here has been executed.** +**Updated 2026-11-19:** §0 is the **DEV vd03 execution plan using the groups and accounts that exist today**, so +it does not wait for scadaproj#58, the D3 automation account or the D6 deploy group. QA keeps the full +prerequisites in §5–§7, and the QA deploy hold still stands. + +--- + +## 0. DEV vd03 now, with today's groups and accounts (2026-11-19) + +### 0.1 What the directory holds today + +Re-enumerated 2026-11-19 from the Mac (`ldapsearch` over LDAPS to nam1, bound as `svc_igntadmin`; that bind is +the D1 interim's single verification bind). +- **Groups:** 41 `UG_WW_*`, the 39 from 08-12 plus `UG_WW_PAR_CVD_Oper` and `UG_WW_PAR_CVD_Super`. Neither is a + platform group, so neither is mapped. **There is still no `UG_WW_APP_DEPLOY_*` group.** +- **Names:** the DEV platform names are exactly as in §4. Copy them with this case. + +| DEV group | Members (2026-11-19) | +|---|---| +| `UG_WW_APP_ADMIN_DEV` (7) | chamalas, millerh5, benjamd2, marting4, dohertj2, oswaltk, Luis Bastidas | +| `UG_WW_APP_IDE_DEV` (6) | chamalas, millerh5, benjamd2, marting4, dohertj2, Luis Bastidas | +| `UG_WW_APP_IDE_RO_DEV` (2) | benjamd2, oswaltk | +| `UG_WW_HIST_ADMIN_DEV` (7) | **the same 7 people as `APP_ADMIN_DEV`** | +| `UG_WW_CITRIX_DEV` (6) | never mapped; culverj holds only this group, so they get no role on DEV | + +**Accounts used on DEV (no new accounts):** + +| Use | Account | Groups and resulting roles | Credential | +|---|---|---|---| +| LDAP lookup (D1 interim) | `svc_igntadmin@nam.zimmer.com` | No `UG_WW_*` group, so it **cannot sign in** to any app, which is correct for a lookup account | Mac Keychain, service `btdb-manager/ldap`. Seeded into each store as `nam-ldap-svc-password` | +| Positive login and automation (D3 option b) | `dohertj2` | `APP_ADMIN_DEV` + `APP_IDE_DEV` + `HIST_ADMIN_DEV`. Gets Administrator everywhere, plus Designer in OtOpcUa and ScadaBridge, plus Deployer in ScadaBridge (§0.2) | Mac Keychain (`NAM\dohertj2`) | +| Negative control: zero roles | `adm_dohertj2` | 3 groups, none `UG_WW_*`. The library passes it (`memberOf` is non-empty), the app maps no role, and §3.2 must refuse it | Mac Keychain (`NAM\adm_dohertj2`) | +| Negative control: bad credentials | a bogus user/password | — | — | + +**Viewer is not exercised live on DEV.** Only benjamd2 and oswaltk hold `APP_IDE_RO_DEV`, and both also hold +`APP_ADMIN_DEV`. The Viewer mapping is checked by reading the effective config back (A4). A real Viewer-only +login waits for QA or for a volunteer. + +### 0.2 Deviations from the full plan (DEV only) + +| Full plan | DEV now | Why it's acceptable | Ends when | +|---|---|---|---| +| D1: dedicated account from scadaproj#58 | `svc_igntadmin` | The interim §5 already allows on DEV. **Tell the Ignition team before §0.4 step 3**: a wrong secret here locks *their* admin account (2 bad binds per login, §1.3) | scadaproj#58 is delivered; swap it in during the soak (§7) | +| D3: a NAM automation account | `dohertj2` (option b) | It holds every DEV role the scripts need | The D3 account exists | +| D6: `UG_WW_APP_DEPLOY_DEV` → Deployer | **`UG_WW_HIST_ADMIN_DEV` → `Deployer`, in ScadaBridge only** | Still one group, one role per app (§3.1): ScadaBridge maps `HIST_ADMIN` to nothing else. Its members are identical to `APP_ADMIN_DEV`, so the effect is "DEV admins can deploy", the SoD collapse already accepted for this directory (`ldap_setup.md`). It is a DEV-only row | D6's group exists: add `APP_DEPLOY_DEV` → Deployer, then delete the `HIST_ADMIN_DEV` row | +| D4: `zimmer-rootca` in `LocalMachine\Root` | Phase 0 checks it. vd03 is domain-joined, so the root is expected to be there via GPO [I]. If it isn't, run DEV with `AllowInsecure=true` and record it | DEV only, short-lived (D4 b) | The root is installed | +| D7: membership confirmed per person | Done for DEV by §0.1 | — | — | + +**Unchanged:** the standards (§3), the LDAP block (§6, with `ServiceAccountDn: svc_igntadmin@nam.zimmer.com`), +the restart rules, the §7.6 verification and stop rule, and the rollback (§7.7). + +### 0.3 Builds on vd03 + +| App | On vd03 (2026-11-19) | Carries | Action | +|---|---|---|---| +| HistorianGateway | `f84af29` | #136 (case-insensitive `GroupToRole`, mapper fault refused) | none | +| MxAccessGateway | `e74918cc` | already refuses zero roles | none | +| OtOpcUa | `cdf433a35` | #913 (§2): options passthrough, zero-role refusal, library logger | none | +| ScadaBridge | **`061432c8`** | **neither #144 nor #145** | **Deploy `main` `2e0ce81e`** (§0.4 step 1) | + +ScadaBridge `061432c8..2e0ce81e` is 11 commits: #144, #145 and the #116 `leader-auto-down` default (already +drilled on vd03, 2026-11-15). **No migration** and no wire change. Use the procedure in +`docs/deployment/deployment-records/2026-11-15-wonder-app-vd03-061432c8.md` (single central + site; take a +DB backup first). With login still off, the dev user holds every role, so #144/#145 have no visible effect +until step 6. + +### 0.4 Order of work on vd03 + +All remote steps stay inside the `winrm` deploy scope (§7). One app at a time; each one passes §7.6 before the next. + +1. **ScadaBridge binary deploy `2e0ce81e`.** Verify with the deploy's normal checks: health, the site connected, + the CLI works as the login-off dev user. +2. **Phase 0 on vd03 (§7.0), reduced:** DC reach on 636 from vd03; the `zimmer-rootca` check (decides D4); + back up every app's config and env; record OtOpcUa `Security__Auth__DisableLogin` (expected `true`), mxgw's + environment name, its `ServerCertificateThumbprintSha256` and base `GwAdmin`/`GwReader`; each app's secrets + store and KEK source; the OtOpcUa `LdapGroupRoleMapping` rows. Builds per §0.3. The service-account bind was + done 2026-11-19 (§0.1), so don't repeat it. +3. **Seed `nam-ldap-svc-password`** in each store (§7.1): HG, mxgw and ScadaBridge Central through their + `/admin/secrets` pages (login is still off on all three), and OtOpcUa's store with the `secret` CLI or its + page. Verify each read-back value with **one** LdapProbe bind as `svc_igntadmin`. +4. **HistorianGateway (the canary), §7.2.** §6 + §4.1 DEV mapping, `Dashboard:DisableLogin=false`. Run §7.6 fully, + including the nam1→nam2 failover check. +5. **MxAccessGateway, §7.3.** §6 + §4.2 DEV mapping; delete the base `GwAdmin`/`GwReader`; remove any GLAuth pin; + `DisableLogin=false`. +6. **ScadaBridge, §7.4.** + - a. **While login is still off**, add the role mappings with the CLI (`--url` the vd03 central): + `UG_WW_APP_ADMIN_DEV`→Administrator, `UG_WW_APP_IDE_DEV`→Designer, `UG_WW_APP_IDE_RO_DEV`→Viewer, + **`UG_WW_HIST_ADMIN_DEV`→Deployer (DEV interim, §0.2)**. The §4.4 SQL fallback works too: put the + `HIST_ADMIN_DEV` row in its `@t`. + - b. Write `ScadaBridge:Security:Ldap` (§6). Remove **both** `DisableLogin` and `AllowOutsideDevelopment`. + - c. Restart the central. Re-point scripts (`apply.sh`, drill and deploy packs) at `dohertj2`, and confirm + `/auth/token` and the CLI (HTTP Basic) work with it. + - d. Extra §7.6 check: `adm_dohertj2` is refused at `/auth/login`, at `/auth/token` **and** on the + management/CLI path (#145). +7. **OtOpcUa AdminUI, §7.5.** §6 as `Security__Ldap__*` with `FallbackServers__0` (the #913 build honours it), + the §4.3 DEV `GroupToRole`, then `Security__Auth__DisableLogin=false`. Restart the single node. §7.6 plus + acceptance A2 (nam1 blocked → login through nam2, with the library's `sticky preference moved` line). + `adm_dohertj2` is refused at `/auth/login` and `/auth/token`. +8. **Record** the run as `docs/deploy/2026-11-
-vd03-nam-ldap-cutover.md` in scadaproj, plus a line in each + app's deployment notes. The mxgw notes must say "delete `GwAdmin`/`GwReader` from the base file on every + redeploy". Tick the DEV items on scadaproj#6. + +**Stop rule (§7.6 rule 6) for this run:** the account is Ignition's, so stop at the **first** `service-bind` +warning, not the second. Ask IT for the account's lockout state before any retry. + +**Soak:** a few working days of real logins on DEV. QA does **not** start from this section: it still needs +scadaproj#58, D3 and D6, and the owner lifting the QA hold. **Goal:** move the login of the four auth-bearing apps off their current setup (disabled login, or a GLAuth test directory) and onto the Zimmer NAM Active Directory: DEV first, a soak, then the QA pair. diff --git a/ldap_mapping.md b/ldap_mapping.md index c5aa883..7cf7649 100644 --- a/ldap_mapping.md +++ b/ldap_mapping.md @@ -81,7 +81,7 @@ made. One role per cell. |---|---|---|---|---|---| | `UG_WW_APP_ADMIN_` | Administrator | Administrator | Administrator | Administrator | | | `UG_WW_APP_IDE_` | Designer | Designer | Viewer | — | **Was "Designer + Deployer" in ScadaBridge.** Resolved: Designer here; `Deployer` comes from the new group below. mxgw has no Designer, so Viewer. | -| `UG_WW_APP_DEPLOY_` | — | Deployer | — | — | **NEW group: owner/IT decision, request by ServiceNow ticket** (cutover plan D6). Until it exists, no NAM user can deploy in ScadaBridge, so the ScadaBridge cutover waits for it. | +| `UG_WW_APP_DEPLOY_` | — | Deployer | — | — | **NEW group: owner/IT decision, request by ServiceNow ticket** (cutover plan D6). Until it exists, no NAM user can deploy in ScadaBridge, so the ScadaBridge cutover waits for it. **DEV interim (2026-11-19, plan §0.2):** ScadaBridge DEV maps `UG_WW_HIST_ADMIN_DEV` → `Deployer` (same 7 members as `APP_ADMIN_DEV`) until this group exists. | | `UG_WW_APP_IDE_RO_` | Viewer | Viewer | Viewer | Viewer | | | `UG_WW_HIST_ADMIN_` | Viewer | — | — | Administrator | OtOpcUa Viewer, because historization targets are authored in the AdminUI and visible to a historian admin, but not editable. | | `UG_WW_BTMGR_RO_` (QA/PROD only) | — | Viewer | — | Viewer | `BTMGR_RO_QA` is **empty** (08-12). |