# SAML Integration Issue - no user email

**URL:** <https://devforum.zoom.us/t/saml-integration-issue-no-user-email/16794>\
**Category:** API and Webhooks\
**Created:** [May 8, 2020, 3:17pm UTC](https://devforum.zoom.us/t/saml-integration-issue-no-user-email/16794 "2020-05-08T15:17:25Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![robertom](https://avatars.discourse-cdn.com/v4/letter/r/67e7ee/32.png) [@robertom](https://devforum.zoom.us/u/robertom)\
**Post date:** [May 8, 2020, 3:17pm UTC](https://devforum.zoom.us/t/saml-integration-issue-no-user-email/16794/1 "2020-05-08T15:17:25Z")

</div>

We are using SSO for our licensed Zoom accounts. Our University’s IDP does not always provide an email address in the returned SAML attributes. Only users who have flagged their email as public get the email attribute. For users with a private email address, we get a string of the form “fixedprefix\_fe0a516ffd3fb78b1fad2693cd1df353”. This looks like some sort of hash – but of what I don’t know. Is there a way to map this hash string back to the original SAML attributes? My goal is to be able to associate a zoom account back to a user from our IDP.

We are using the API with JWT and various endpoints require us to specify a user by email address or zoom id. For accounts that only have the hash string instead of an email address, we can only use the zoom id. But we don’t have an easy way to get that id from the original user info without a one-to-one mapping from our data to zoom accounts.

---

<div class="post-metadata">

**Author:** ![michael.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael.zoom/32/37213_2.png) [@michael.zoom](https://devforum.zoom.us/u/michael.zoom)\
**Post date:** [May 13, 2020, 3:29pm UTC](https://devforum.zoom.us/t/saml-integration-issue-no-user-email/16794/2 "2020-05-13T15:29:31Z")

</div>

Hi @robertom, pardon I’m not entirely sure yet. Are you using the [SCIM2 API to List Users](https://marketplace.zoom.us/docs/api-reference/scim-api/user/userscim2list)? Are these hashed private emails returned for your account?

Pardon my inability to test here, IDP setups being different make it difficult to reproduce this.

---

<div class="post-metadata">

**Author:** ![robertom](https://avatars.discourse-cdn.com/v4/letter/r/67e7ee/32.png) [@robertom](https://devforum.zoom.us/u/robertom)\
**Post date:** [May 13, 2020, 8:47pm UTC](https://devforum.zoom.us/t/saml-integration-issue-no-user-email/16794/3 "2020-05-13T20:47:40Z")

</div>

Hi @michael.zoom. I’m using the regular Zoom API. I’ll check out the SCIM2 API option, but I’m not totally clear on the difference.

Thanks,  
Roberto

---

<div class="post-metadata">

**Author:** ![michael.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael.zoom/32/37213_2.png) [@michael.zoom](https://devforum.zoom.us/u/michael.zoom)\
**Post date:** [May 13, 2020, 8:50pm UTC](https://devforum.zoom.us/t/saml-integration-issue-no-user-email/16794/4 "2020-05-13T20:50:36Z")

</div>

The [SCIM2 API](https://marketplace.zoom.us/docs/api-reference/scim-api) (System for Cross-identity Management 2.0) provides support for user provisioning with SSO / IDPs. Let me know if your SAML attributes map over here, or if there’s anything I can help with further.

---

<div class="post-metadata">

**Author:** ![DeveloperBot](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/developerbot/32/12632_2.png) [@DeveloperBot](https://devforum.zoom.us/u/DeveloperBot)\
**Post date:** [August 21, 2020, 9:18pm UTC](https://devforum.zoom.us/t/saml-integration-issue-no-user-email/16794/5 "2020-08-21T21:18:01Z")

</div>

Closed on August 21, 2020, 9:18pm UTC


