A mismatched client certificate and key pair is now ignored and logged instead of installed.
What's wrong with this entry?
When CLAUDE_CODE_CLIENT_CERT and CLAUDE_CODE_CLIENT_KEY do not belong together, typically mid-rotation, the loader now logs "mTLS: Ignoring mismatched client cert/key pair" and keeps the previously loaded pair rather than installing a broken one.
- The pair is verified with Node's
X509Certificate.checkPrivateKey, honouringCLAUDE_CODE_CLIENT_KEY_PASSPHRASE. - Certificate blocks are located with a new PEM block pattern, so a bundle containing several certificates is handled.
mTLS: Ignoring mismatched client cert/key pair
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.228
Bundled API client: new endpoints and a stripped request field
Both mention client
-
v2.1.228
Bundled Anthropic SDK picks up beta resources
Both mention client
-
v2.1.228
API client request handling moved to a middleware chain
Both mention client