{"version":"2.1.232","anchor":"gateway-tls-pin-mismatch-names-both-certificates","canonical_anchor":"gateway-tls-pin-mismatch-names-both-certificates","heading":"Gateway TLS pin mismatch names both certificates","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/gateway-tls-pin-mismatch-names-both-certificates","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Gateway TLS pin mismatch names both certificates\n\nA gateway certificate pin mismatch now shows both the presented and the trusted fingerprint.\n\n**What**\n\nWhen the cloud gateway presents a certificate that does not match the pinned fingerprint, the sign-in failure message can now name the fingerprint that was presented as well as the one that was trusted.\n\n**Details**\n\n- Both fingerprints are attached to the thrown error, and a new extractor reads them off the error or its `cause`.\n\n**Evidence**\n\n`gateway TLS certificate does not match the pinned fingerprint`\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}