docs(security): per-instance credential references (#835) and the user-certificate directory (#836)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Joseph Doherty
2026-11-11 03:52:48 -05:00
parent 63331b0416
commit 0810e808c9
4 changed files with 112 additions and 4 deletions
+13
View File
@@ -540,6 +540,19 @@ deploy that recreates the driver), not on `ReinitializeAsync`. The init log line
`transport=Libplctag (node default)` when the pin is what selected the stack. There is **no AbLegacy
counterpart**: an AbLegacy driver with no key always runs libplctag (Native is opt-in per driver).
### `Drivers:OpcUaClient:UserCertificateDirectory` (user-certificate directory, #836)
- **Purpose:** the ONLY directory an OpcUaClient driver's `UserCertificatePath` (user-certificate identity) may load a
PFX from. The authored path is relative to it (`plant1/user.pfx`); absolute / UNC / drive paths and `..` are refused
at save, deploy, Test Connect and browse, and the resolved path — symbolic links / junctions included — must stay
inside it at load time. See [`security.md`](security.md) §"Key-material file paths are confined to a node directory".
- **Read** once at startup in `Program.cs` (`OpcUaUserCertificatePaths.Configure`) on every node: the driver (driver
role) and the AdminUI live browse (admin role) both load user certificates, so keep the same relative layout on both.
| Key | Type | Default | Meaning |
|---|---|---|---|
| `UserCertificateDirectory` | string | `<LocalAppData>/OtOpcUa/pki/user-certificates` | Directory (made absolute at startup). Env form: `Drivers__OpcUaClient__UserCertificateDirectory`. ACL it to the service account + administrators. |
### `Drivers:Galaxy:AckIdentityCache` (cached API-key → Galaxy ack identity set, #765)
- **Purpose:** the node-wide set of API key ids that have a Galaxy ack identity (a `galaxy-ack-user` secret),