Answer: OneLogin SSO login to Claude fails because OneLogin user profiles contain distinct fields for username and email that may hold different values, and the SCIM parameters and SAML attribute statements are configured independently and can each pull from a different field. Claude requires an exact string match, so a common mismatch occurs when the SCIM parameters tab maps the email attribute to Username while the SAML attribute statement sends the Email field. Status: Confirmed Entry: tool/claude-apps/troubleshooting/onelogin-sso-scim-email-mismatch-cause Revision: 4 Digest: sha256:45177582853d17cb (changes whenever the content changes) Timeline: Created: 2026-11-13T02:59:04Z Last changed: 2026-11-19T12:01:46Z (Tabs to align: — → Both must be checked and aligned) Last verified: 2026-11-20T12:05:14Z Next check: 2026-11-21T12:05:14Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Requirement | exact string match | [1] | 2026-11-20 Cause | distinct fields for username and email, which may hold different values | [1] | 2026-11-20 Configuration independence | configured independently and can each pull from a different field | [1] | 2026-11-20 Common mismatch | the SCIM parameters tab maps the email attribute to Username | [1] | 2026-11-20 Recommended field | Recommended for both SCIM and SAML | [1] | 2026-11-20 Tabs to align | Both must be checked and aligned | [1] | 2026-11-20 Sources: [1] Anthropic. "OneLogin SSO/SCIM email mismatch | Claude Help Center". https://support.claude.com/en/articles/13917861-onelogin-sso-scim-email-mismatch Role: primary. Accessed: 2026-11-20T12:05:14Z Quote: "Claude requires an exact string match" (Supports: Requirement) Quote: "OneLogin user profiles contain distinct fields for username and email, which may hold different values." (Supports: Cause) Quote: "SCIM provisioning parameters and SAML attribute statements are configured independently and can each pull from a different field" (Supports: Configuration independence) Quote: "the SCIM parameters tab maps the email attribute to Username (which may be an employee ID or short name) while the SAML attribute statement sends the Email field" (Supports: Common mismatch) Quote: "Recommended for both SCIM and SAML" (Supports: Recommended field) Quote: "Both must be checked and aligned." (Supports: Tabs to align) Snapshot SHA-256: 73dff3f14b3dc8df2b3afa97d63f87da820f261182baaeb554fbd9eda707faba (captured 2026-11-19T12:01:47Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-19T12:01:46Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:05:14Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:05:14Z Last attempt: 2026-11-20T12:05:14Z Notes and limitations: Extracted automatically from a single official source (section "How this happens"). Related: https://latestn.com/tool/claude-apps/troubleshooting/org-repos-missing-github Why don't my organization's GitHub repositories appear after connecting in Claude? https://latestn.com/tool/claude-apps/troubleshooting/output-blocked-content-filtering-error Why am I getting an 'Output blocked by content filtering policy' error in Claude? https://latestn.com/tool/claude-apps/troubleshooting/output-blocked-content-filtering-error-2 Why does Claude show an 'Output blocked by content filtering policy' error? https://latestn.com/tool/claude-apps/troubleshooting/not-authenticated-with-api-key How do I fix 'Not authenticated' in Claude Code even though I set ANTHROPIC_API_KEY? https://latestn.com/tool/claude-apps/troubleshooting/npm-eacces-permission-denied How do I fix EACCES or permission denied errors when running npm install for Claude Code? https://latestn.com/tool/claude-apps/troubleshooting/okta-sso-scim-email-mismatch-fix How do I fix an Okta SSO/SCIM email mismatch in Claude? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-19T12:01:46Z | changed | Tabs to align: — → Both must be checked and aligned | [1] 2026-11-19T12:01:46Z | changed | Recommended field: — → Recommended for both SCIM and SAML | [1] 2026-11-19T12:01:46Z | changed | Configuration independence: — → configured independently and can each pull from a different field | [1] 2026-11-19T12:01:46Z | changed | Resolution: Both must be checked and aligned → — | [1] 2026-11-19T12:01:46Z | changed | Common mismatch: maps the email attribute to Username → the SCIM parameters tab maps the email attribute to Username | [1] 2026-11-19T12:01:46Z | changed | Configuration issue: configured independently and can each pull from a different field → — | [1] 2026-11-18T12:02:02Z | changed | Resolution: — → Both must be checked and aligned | [1] 2026-11-18T12:02:02Z | changed | Common mismatch: — → maps the email attribute to Username | [1] 2026-11-18T12:02:02Z | changed | Configuration issue: — → configured independently and can each pull from a different field | [1] 2026-11-18T12:02:02Z | changed | Cause: — → distinct fields for username and email, which may hold different values | [1] 2026-11-18T12:02:02Z | changed | Requirement: — → exact string match | [1] 2026-11-18T12:02:02Z | changed | recommended field: Recommended for both SCIM and SAML → — | [1] 2026-11-18T12:02:02Z | changed | configuration independence: SCIM provisioning parameters and SAML attribute statements are configured independently and can each pull from a different field → — | [1] 2026-11-18T12:02:02Z | changed | profile fields: OneLogin user profiles contain distinct fields for username and email, which may hold different values → — | [1] 2026-11-18T12:02:02Z | changed | common mismatch: the SCIM parameters tab maps the email attribute to Username (which may be an employee ID or short name) while the SAML attribute statement sends the Email field → — | [1] 2026-11-18T12:02:02Z | changed | requirement: exact string match → — | [1] 2026-11-17T12:07:10Z | changed | recommended field: — → Recommended for both SCIM and SAML | [1] 2026-11-17T12:07:10Z | changed | configuration independence: — → SCIM provisioning parameters and SAML attribute statements are configured independently and can each pull from a different field | [1] 2026-11-17T12:07:10Z | changed | profile fields: — → OneLogin user profiles contain distinct fields for username and email, which may hold different values | [1] 2026-11-17T12:07:10Z | changed | common mismatch: — → the SCIM parameters tab maps the email attribute to Username (which may be an employee ID or short name) while the SAML attribute statement sends the Email field | [1] 2026-11-17T12:07:10Z | changed | requirement: — → exact string match | [1] 2026-11-17T12:07:10Z | changed | Recommended field: Recommended for both SCIM and SAML → — | [1] 2026-11-17T12:07:10Z | changed | Configuration note: SCIM provisioning parameters and SAML attribute statements are configured independently and can each pull from a different field → — | [1] 2026-11-17T12:07:10Z | changed | Root cause: OneLogin user profiles contain distinct fields for username and email, which may hold different values → — | [1] 2026-11-17T12:07:10Z | changed | Common mismatch: the SCIM parameters tab maps the email attribute to Username (which may be an employee ID or short name) while the SAML attribute statement sends the Email field → — | [1] 2026-11-17T12:07:10Z | changed | Requirement: exact string match → — | [1] 2026-11-13T02:59:04Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-apps/troubleshooting/onelogin-sso-scim-email-mismatch-cause/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-apps/troubleshooting/onelogin-sso-scim-email-mismatch-cause POST: https://latestn.com/dispute/tool/claude-apps/troubleshooting/onelogin-sso-scim-email-mismatch-cause with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-apps/troubleshooting/onelogin-sso-scim-email-mismatch-cause?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). Why does OneLogin SSO login to Claude fail with an email mismatch or blocked account creation? Revision 4, last verified 2026-11-20T12:05:14Z. https://latestn.com/tool/claude-apps/troubleshooting/onelogin-sso-scim-email-mismatch-cause (accessed 2026-11-21T10:05:23Z). @misc{LatestN_tool_claude_apps_troubleshooting_onelogin_sso_scim_email_mismatch_cause_r4, title = {Why does OneLogin SSO login to Claude fail with an email mismatch or blocked account creation?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-apps/troubleshooting/onelogin-sso-scim-email-mismatch-cause}}, note = {Revision 4; digest sha256:45177582853d17cb; last verified 2026-11-20T12:05:14Z; accessed 2026-11-21T10:05:23Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-apps/troubleshooting/onelogin-sso-scim-email-mismatch-cause