test(validation): SDK compatibility matrix uses the production 65-char API key, adds #880 format cases
The cross-version matrix (#782) used a 55-char 'otua_matrix_' key, which stayed under SDK 2's 64-byte RsaEncryptedSecret threshold and hid #880. It now uses the ApiKeySecret.Generate shape (65 chars, random per run, never recorded). Every Shared leg adds production-length-API-key-wrong-secret-reaches-key-check, which must get BadIdentityTokenRejected rather than a format failure. SDK 2 clients also add sdk2-default-RsaEncryptedSecret-control, the negative control: the SDK's default handler must be refused with BadIdentityTokenInvalid by a 1.x server and admitted by an SDK 2 server. The runner passes the server SDK version from ready.json. Claude-Session: https://claude.ai/code/session_01GT67ACmpMR7b9LGRPLijMi
This commit is contained in:
@@ -39,6 +39,19 @@ random, API-key-shaped credential from the process environment; production
|
||||
ACL, write and condition-method checks use the resulting key identity. This
|
||||
fixture does not replace cryptographic API-key-authenticator coverage.
|
||||
|
||||
The credential has the production `ApiKeySecret.Generate` shape and length,
|
||||
65 characters (lmxopcua#880). The 55-character key used before then stayed
|
||||
under SDK 2's 64-byte threshold, so it hid a real failure. SDK 2.0.1's own
|
||||
UserName handler sends a longer password as an `RsaEncryptedSecret`, and an
|
||||
SDK 1.5 server rejects that with `BadIdentityTokenInvalid`. The production
|
||||
clients (Shared/CLI and the driver) force the legacy RSA format. Every Shared
|
||||
leg adds two cases. The first sends a wrong secret of the same length, which
|
||||
must reach the key check (`BadIdentityTokenRejected`, not a format failure).
|
||||
The second runs only on an SDK 2 client and is the negative control: the
|
||||
SDK's default handler with the valid key must be refused with
|
||||
`BadIdentityTokenInvalid` by a 1.x server and admitted by an SDK 2 server.
|
||||
The Shared client passes the server's SDK version from `ready.json` for it.
|
||||
|
||||
The driver and actual CLI run in a disposable `--network none` Linux container,
|
||||
alongside a separate baseline or candidate server process. PKI lives only in
|
||||
the mounted task directory; no host profile PKI or fleet endpoint is touched.
|
||||
|
||||
Reference in New Issue
Block a user