{"version":"2.1.227","anchor":"auth-failures-now-name-the-credential-source","canonical_anchor":"auth-failures-now-name-the-credential-source","heading":"Auth failures now name the credential source","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/auth-failures-now-name-the-credential-source","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Auth failures now name the credential source\n\nAuth failures now name where the bad credential came from, like your custom headers.\n\n**What**\n\nWhen a request is rejected and the credentials came from headers rather than a plain API key, the error now names the actual source: `ANTHROPIC_CUSTOM_HEADERS`, an external auth token, or an external API key, with the server's own message appended after a middot.\n\n**Details**\n\n- Previously these fell through to the generic x-api-key wording, which pointed at a setting the user was not using.\n- Credentials from a managed key or from a claude.ai login are classified as an authentication failure instead.\n\n**Evidence**\n\n`Invalid ANTHROPIC_CUSTOM_HEADERS`\n\n- Area: Auth\n- Names: `ANTHROPIC_CUSTOM_HEADERS`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}