{"version":"2.1.232","anchor":"login-can-no-longer-double-submit-and-gateway-errors-are-sho","canonical_anchor":"login-can-no-longer-double-submit-and-gateway-errors-are-sho","heading":"Login can no longer double-submit, and gateway errors are shown","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/login-can-no-longer-double-submit-and-gateway-errors-are-sho","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Login can no longer double-submit, and gateway errors are shown\n\nLogin can't double-submit, and a gateway certificate problem is shown instead of a silent relaunch.\n\n**What**\n\nThe login dialog holds a reference that lets its completion callback fire at most once. On account switch, the enrollment path passes the previous gateway credentials and returns a login error or a relaunch signal, so a gateway certificate mismatch is reported as a system message instead of silently relaunching.\n\n**Evidence**\n\n`previousGatewayAuth`\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}