Answer: Align the email attribute mappings across SSO and SCIM layers, then trigger a full re-sync. For PingOne, ensure emails[primary].value and the SAML/OIDC email attribute or claim both map to PingOne's Email Address attribute; for PingFederate, ensure the email attribute's source is the same LDAP or data store attribute used in your SCIM outbound provisioning channel. Status: Confirmed Entry: tool/claude-apps/troubleshooting/fix-ping-identity-email-mismatch Revision: 2 Digest: sha256:1e76bf3df51b8f1d (changes whenever the content changes) Timeline: Created: 2026-11-13T11:56:55Z Last changed: 2026-11-20T12:05:17Z (PingFederate email source: — → same LDAP or data store attribute used in your SCIM outbound provisioning channel) Last verified: 2026-11-20T12:05:17Z Next check: 2026-11-21T12:05:17Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of PingOne SCIM mapping | emails[primary].value | [1] | 2026-11-20 PingOne SAML/OIDC mapping | email attribute or claim | [1] | 2026-11-20 PingFederate email source | same LDAP or data store attribute used in your SCIM outbound provisioning channel | [1] | 2026-11-20 Sync requirement | Full sync required | [1] | 2026-11-20 PingOne full sync action | trigger a full provisioning cycle | [1] | 2026-11-20 PingFederate full sync action | Trigger a full sync in your outbound provisioning channel. | [1] | 2026-11-20 Sources: [1] Anthropic. "Ping Identity SSO/SCIM email mismatch | Claude Help Center". https://support.claude.com/en/articles/13917875-ping-identity-sso-scim-email-mismatch Role: primary. Accessed: 2026-11-20T12:05:17Z Quote: "Ensure emails[primary].value maps to PingOne's Email Address attribute." (Supports: PingOne SCIM mapping) Quote: "Ensure the email attribute or claim also maps to PingOne's Email Address attribute." (Supports: PingOne SAML/OIDC mapping) Quote: "Ensure its source is the same LDAP or data store attribute used in your SCIM outbound provisioning channel." (Supports: PingFederate email source) Quote: "Critical — Full sync required: An incremental sync will not update existing records after you change an attribute mapping." (Supports: Sync requirement) Quote: "In the app's provisioning settings, trigger a full provisioning cycle." (Supports: PingOne full sync action) Quote: "PingFederate: Trigger a full sync in your outbound provisioning channel." (Supports: PingFederate full sync action) Snapshot SHA-256: 4a42516b4b3abd70a7c184074a8f9ff153435b93f65310c540b196d985733d21 (captured 2026-11-19T12:01:49Z) 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:49Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:05:17Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:05:17Z Last attempt: 2026-11-20T12:05:17Z Notes and limitations: Extracted automatically from a single official source (section "Resolution"). Related: https://latestn.com/tool/claude-apps/troubleshooting/foundry-support-options Where can I get support while using Claude through Microsoft Foundry? https://latestn.com/tool/claude-apps/troubleshooting/get-help-still-stuck Where can I find more resources or get help if I'm still stuck with Claude Code? https://latestn.com/tool/claude-apps/troubleshooting/grant-checkboxes-grey-missing Why are the grant checkboxes grey or the Grants page missing when assigning a program to a custom role in Claude Enterprise? https://latestn.com/tool/claude-apps/troubleshooting/fix-api-connection-error How do I fix an API connection error in Claude? https://latestn.com/tool/claude-apps/troubleshooting/fix-google-workspace-sso-scim-email-mismatch How do I fix a Google Workspace SSO/SCIM email mismatch in Claude? https://latestn.com/tool/claude-apps/troubleshooting/fix-login-errors How do I fix a Claude login error? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T12:05:17Z | changed | PingFederate email source: — → same LDAP or data store attribute used in your SCIM outbound provisioning channel | [1] 2026-11-20T12:05:17Z | changed | PingOne SAML/OIDC mapping: — → email attribute or claim | [1] 2026-11-20T12:05:17Z | changed | PingOne SCIM mapping: — → emails[primary].value | [1] 2026-11-20T12:05:17Z | changed | SAML/OIDC mapping: email attribute or claim → — | [1] 2026-11-20T12:05:17Z | changed | SCIM mapping: emails[primary].value → — | [1] 2026-11-17T12:07:14Z | recovered | Check succeeded again | — 2026-11-16T11:56:21Z | check-failed | Extraction did not pass verification: answer does not contain any extracted value | — 2026-11-13T11:56:55Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-apps/troubleshooting/fix-ping-identity-email-mismatch/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/fix-ping-identity-email-mismatch POST: https://latestn.com/dispute/tool/claude-apps/troubleshooting/fix-ping-identity-email-mismatch with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-apps/troubleshooting/fix-ping-identity-email-mismatch?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I fix a Ping Identity SSO/SCIM email mismatch in Claude? Revision 2, last verified 2026-11-20T12:05:17Z. https://latestn.com/tool/claude-apps/troubleshooting/fix-ping-identity-email-mismatch (accessed 2026-11-21T10:07:51Z). @misc{LatestN_tool_claude_apps_troubleshooting_fix_ping_identity_email_mismatch_r2, title = {How do I fix a Ping Identity SSO/SCIM email mismatch in Claude?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-apps/troubleshooting/fix-ping-identity-email-mismatch}}, note = {Revision 2; digest sha256:1e76bf3df51b8f1d; last verified 2026-11-20T12:05:17Z; accessed 2026-11-21T10:07:51Z} } 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/fix-ping-identity-email-mismatch