{"version":"2.1.323","anchor":"oauth-org-not-allowed-flag-and-network-errors-marked-as-noa","canonical_anchor":"oauth-org-not-allowed-flag-and-network-errors-marked-as-noa","heading":"Credential checks now tell org-blocked logins and network failures apart","tier":"internal","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/oauth-org-not-allowed-flag-and-network-errors-marked-as-noa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Credential checks now tell org-blocked logins and network failures apart\n\nChecking your credentials now records separately when your organization does not allow the login, and when the server could not be reached at all\n\n**What**\n\nWhen Claude Code checks whether your login or key works, it now records two outcomes that were previously grouped with others:\n\n- A login that fails because your organization does not allow that OAuth sign-in. OAuth is the browser-based \"sign in with your account\" method. Before, this only counted as a general sign-in failure.\n\n- A network error, meaning no answer came back from the server. Before, this was only marked as something worth retrying.\n\n**Why**\n\nThe rest of Claude Code can now tell an organization restriction apart from a wrong credential, and an unreachable network apart from a rejected key. These cases need different fixes: asking an administrator, signing in again, or checking your connection.\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}