{"version":"2.1.315","anchor":"stored-login-check-now-has-a-refusal-reason-and-an-abortable","canonical_anchor":"stored-login-check-now-has-a-refusal-reason-and-an-abortable","heading":"Refused stored logins can now carry a reason from your administrator","tier":"notice","area":"Auth","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/stored-login-check-now-has-a-refusal-reason-and-an-abortable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Refused stored logins can now carry a reason from your administrator\n\nWhen an administrator's settings refuse a stored login, Claude Code can now report the reason instead of a fixed error\n\n**Unclear.** It is not clear what message a refused user now sees, or when the refusal reason appears.\n\n**What**\n\nThe check on your stored login has been reworked. This is the login Claude Code saved from an earlier sign-in. The check can now work out a reason why an administrator's settings refuse it. When that happens, the error Claude Code raises carries the reason, where before it showed a fixed error.\n\nThe step that waits for the login to be confirmed can now be cancelled partway through. When an administrator forces login through a gateway, which is a server that sits between Claude Code and the model provider, Claude Code now works out the gateway's address from a different source.\n\n**Why**\n\nThis affects what you see when a login, or a key supplied through a managed `apiKeyHelper`, is refused.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}