Answer: Align both mappings to the same Okta field by using user.email for both SCIM and SSO, then force a full re-sync since an incremental sync will not update existing records. Status: Confirmed Entry: tool/claude-apps/troubleshooting/okta-sso-scim-email-mismatch-fix Revision: 2 Digest: sha256:4c1e2219b04a3d05 (changes whenever the content changes) Timeline: Created: 2026-11-13T02:59:02Z Last changed: 2026-11-20T12:05:11Z (Push users location: — → Push Now) Last verified: 2026-11-20T12:05:11Z Next check: 2026-11-21T12:05:11Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of SCIM mapping source | user.email | [1] | 2026-11-20 SAML SSO claim value | user.email | [1] | 2026-11-20 OIDC email claim | user.email | [1] | 2026-11-20 Sync type required | Full sync required | [1] | 2026-11-20 Force sync location | Force Sync | [1] | 2026-11-20 Push users location | Push Now | [1] | 2026-11-20 Sources: [1] Anthropic. "Okta SSO/SCIM email mismatch | Claude Help Center". https://support.claude.com/en/articles/13917840-okta-sso-scim-email-mismatch Role: primary. Accessed: 2026-11-20T12:05:11Z Quote: "change the email (or userName ) source to user.email" (Supports: SCIM mapping source) Quote: "change the email attribute value to user.email" (Supports: SAML SSO claim value) Quote: "update the email claim to map to user.email" (Supports: OIDC email claim) Quote: "Critical — Full sync required: An incremental sync will not update existing records after you change an attribute mapping." (Supports: Sync type required) Quote: "In Provisioning → To App , click “Force Sync” to trigger a full re-evaluation of everyone assigned." (Supports: Force sync location) Quote: "Provisioning → Push Users → select affected people → Push Now ." (Supports: Push users location) Snapshot SHA-256: 5534a6f440c6ed6687fdee8311dafa997bbdf4ece0863b3f8d24dfaa09aa3a39 (captured 2026-11-19T12:01:41Z) 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:41Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:05:11Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:05:11Z Last attempt: 2026-11-20T12:05:11Z Notes and limitations: Extracted automatically from a single official source (section "Resolution"). Related: https://latestn.com/tool/claude-apps/troubleshooting/onelogin-sso-scim-email-mismatch-cause Why does OneLogin SSO login to Claude fail with an email mismatch or blocked account creation? 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/node-version-not-supported How do I fix 'Node version not supported' or a silent crash when launching Claude Code? 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/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T12:05:11Z | changed | Push users location: — → Push Now | [1] 2026-11-20T12:05:11Z | changed | OIDC email claim: — → user.email | [1] 2026-11-20T12:05:11Z | changed | SAML SSO claim value: — → user.email | [1] 2026-11-20T12:05:11Z | changed | System log path: Reports → System Log → — | [1] 2026-11-20T12:05:11Z | changed | Push users path: Provisioning → Push Users → — | [1] 2026-11-20T12:05:11Z | changed | Force sync location: Provisioning → To App → Force Sync | [1] 2026-11-20T12:05:11Z | changed | SSO OIDC claim mapping: user.email → — | [1] 2026-11-20T12:05:11Z | changed | SSO SAML attribute value: user.email → — | [1] 2026-11-13T02:59:02Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-apps/troubleshooting/okta-sso-scim-email-mismatch-fix/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/okta-sso-scim-email-mismatch-fix POST: https://latestn.com/dispute/tool/claude-apps/troubleshooting/okta-sso-scim-email-mismatch-fix with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-apps/troubleshooting/okta-sso-scim-email-mismatch-fix?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I fix an Okta SSO/SCIM email mismatch in Claude? Revision 2, last verified 2026-11-20T12:05:11Z. https://latestn.com/tool/claude-apps/troubleshooting/okta-sso-scim-email-mismatch-fix (accessed 2026-11-21T10:05:21Z). @misc{LatestN_tool_claude_apps_troubleshooting_okta_sso_scim_email_mismatch_fix_r2, title = {How do I fix an Okta SSO/SCIM email mismatch in Claude?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-apps/troubleshooting/okta-sso-scim-email-mismatch-fix}}, note = {Revision 2; digest sha256:4c1e2219b04a3d05; last verified 2026-11-20T12:05:11Z; accessed 2026-11-21T10:05:21Z} } 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/okta-sso-scim-email-mismatch-fix