{"version":"2.1.232","anchor":"a-tls-pin-mismatch-right-after-gateway-sign-in-discards-the-","canonical_anchor":"a-tls-pin-mismatch-right-after-gateway-sign-in-discards-the-","heading":"A TLS pin mismatch right after gateway sign-in discards the credential","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/a-tls-pin-mismatch-right-after-gateway-sign-in-discards-the-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### A TLS pin mismatch right after gateway sign-in discards the credential\n\nA certificate pin mismatch right after gateway sign-in deletes the fresh credential and exits with an explanation.\n\n**What**\n\nIf 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.\n\n**Details**\n\n- The fetch extracts the pinned and presented certificate fingerprints into a `gatewayPinMismatch` field.\n- The exit message names both fingerprints (truncated) and the usual causes: several gateway nodes serving different certificates, or TLS interception on the network path.\n- If the credential cannot be removed, a warning is logged and the session still ends.\n\n**Evidence**\n\n`[gateway-login] could not remove the discarded credential from secure storage`\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}