# Are Auth0 Id's senstive

**URL:** <https://community.auth0.com/t/are-auth0-ids-senstive/71117>\
**Category:** Get Help\
**Tags:** security, auth0\
**Created:** [October 11, 2021, 9:21am UTC](https://community.auth0.com/t/are-auth0-ids-senstive/71117 "2021-10-11T09:21:42Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![philip2](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/philip2/32/25433_2.png) [@philip2](https://community.auth0.com/u/philip2)\
**Post date:** [October 11, 2021, 9:21am UTC](https://community.auth0.com/t/are-auth0-ids-senstive/71117/1 "2021-10-11T09:21:43Z")

</div>

Hi All,

I’m hoping someone can help me with this.

Does anyone know if the Auth0 id’s from both email and social connects are “sensitive” currently we’re using them as our userId’s in our API’s and I’m worried that exposing these in the JSON (and in some places the HTML sources) would be bad practice.

Thanks,  
Phil

---

<div class="post-metadata">

**Author:** ![jeff0](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jeff0/32/30027_2.png) [@jeff0](https://community.auth0.com/u/jeff0)\
**Post date:** [October 11, 2021, 12:01pm UTC](https://community.auth0.com/t/are-auth0-ids-senstive/71117/2 "2021-10-11T12:01:59Z")

</div>

Hi @philip2

Thank you for contacting Auth0 Community.

Can you please elaborate what do you mean by Auth0 id’s ? Are you speaking about email addresses or user id like `auth0|xxxx` ?

Thank you  
Jeff

---

<div class="post-metadata">

**Author:** ![dantswain](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dantswain/32/44237_2.png) [@dantswain](https://community.auth0.com/u/dantswain)\
**Post date:** [February 1, 2023, 6:45pm UTC](https://community.auth0.com/t/are-auth0-ids-senstive/71117/3 "2023-02-01T18:45:38Z")

</div>

Hi!

I also would like to know the answer to this question. Specifically I mean the `auth0|xxxx` or `google-oauth2|xxxx` ids. My expectation is that these are not sensitive as they are more or less useless to anyone who doesn’t have an API key, but wanted to verify that.

Thanks!

---

<div class="post-metadata">

**Author:** ![ty.frith](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ty.frith/32/58484_2.png) [@ty.frith](https://community.auth0.com/u/ty.frith)\
**Post date:** [February 2, 2023, 12:03am UTC](https://community.auth0.com/t/are-auth0-ids-senstive/71117/4 "2023-02-02T00:03:15Z")

</div>

Hey there @dantswain welcome to the community!

> [@dantswain](#):
>
> Specifically I mean the `auth0|xxxx` or `google-oauth2|xxxx` ids. My expectation is that these are not sensitive as they are more or less useless to anyone who doesn’t have an API key, but wanted to verify that.

I agree with you in that without credentials someone couldn’t do much (API actions), but I believe `google-oauth2|xxxx` IDs for example could be traced as it’s used across the board for login with Google services.

---

<div class="post-metadata">

**Author:** ![dantswain](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dantswain/32/44237_2.png) [@dantswain](https://community.auth0.com/u/dantswain)\
**Post date:** [February 2, 2023, 12:59am UTC](https://community.auth0.com/t/are-auth0-ids-senstive/71117/6 "2023-02-02T00:59:06Z")

</div>

Thank you! Am I interpreting this correctly in that the risk would essentially be that someone’s accounts could be correlated across tenants? Would that be limited to auth0 clients or also other services that do not interact with auth0 but do use (for example) google oauth2?

---

<div class="post-metadata">

**Author:** ![ty.frith](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ty.frith/32/58484_2.png) [@ty.frith](https://community.auth0.com/u/ty.frith)\
**Post date:** [February 2, 2023, 2:22am UTC](https://community.auth0.com/t/are-auth0-ids-senstive/71117/7 "2023-02-02T02:22:36Z")

</div>

No problem! the Auth0 database connection ID (`auth0|xxxx`) will be unique across tenants - If a user authenticates via a Google connection (`google-oauth2|xxxx`) then that ID could potentially be traced to other services. I’m doing some research on my end just to be sure 😄

---

<div class="post-metadata">

**Author:** ![ty.frith](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ty.frith/32/58484_2.png) [@ty.frith](https://community.auth0.com/u/ty.frith)\
**Post date:** [February 3, 2023, 1:51am UTC](https://community.auth0.com/t/are-auth0-ids-senstive/71117/8 "2023-02-03T01:51:05Z")

</div>

Adding some color here - When a user utilizes a Google Connection to perform authentication via the Google upstream IdP - a redirect occurs to Google and upon successful authentication it (Google) creates its own session. Just like CIC (Auth0). `google-oauth2|xxxx` is the identifier of the user in Auth0, referenced via the Auth0 established session; `xxxx` is the identifier of the user in Google, referenced via the session that Google establishes.

The OIDC solution for this is PPID (defined below) - I believe Apple is the only provider that implements this.

> Pairwise Pseudonymous Identifier (PPID)  
> Identifier that identifies the Entity to a Relying Party that cannot be correlated with the Entity’s PPID at another Relying Party.

Hope this helps to clarify!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [February 17, 2023, 1:51am UTC](https://community.auth0.com/t/are-auth0-ids-senstive/71117/9 "2023-02-17T01:51:10Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
