Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.232 Home All releases ←olderv2.1.231 v2.1.233newer→
Claude Code v2.1.232

A TLS pin mismatch right after gateway sign-in discards the credential

You'll notice
Useful2 Signal2
Auth

A certificate pin mismatch right after gateway sign-in deletes the fresh credential and exits with an explanation.

What

If the first managed-settings request after signing in to an enterprise gateway hits a certificate pin mismatch, the credential that was just stored is deleted from secure storage and the session exits with an explanation instead of leaving a credential behind that will keep failing.

Details
  • The fetch extracts the pinned and presented certificate fingerprints into a gatewayPinMismatch field.
  • The exit message names both fingerprints (truncated) and the usual causes: several gateway nodes serving different certificates, or TLS interception on the network path.
  • If the credential cannot be removed, a warning is logged and the session still ends.
Evidence

[gateway-login] could not remove the discarded credential from secure storage

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.

See this entry in the whole of v2.1.232 →