{"version":"2.1.248","anchor":"console-profile-login-refusals-are-classified","canonical_anchor":"console-profile-login-refusals-are-classified","heading":"Console profile login refusals are classified","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/console-profile-login-refusals-are-classified","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Console profile login refusals are classified\n\nConsole profile login refusals now say which condition blocked you, like an API key in your environment.\n\n**What**\n\nWhen logging into a Console profile is refused, the refusal now carries a specific class such as a workload-identity environment quad, a third-party provider, an API key in the environment, a foreign profile, or a custom credentials path, and a table decides which of those are hard refusals.\n\n**Details**\n\n- The `ANTHROPIC_API_KEY` refusal now only fires when the credential actually in use came from that environment variable.\n- Profile names are validated: only `A-Z a-z 0-9 _ . -` are allowed, and `.` and `..` are rejected.\n\n**Evidence**\n\n`Console profile login refused: non-dispatching env API key present`\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}