# Email verification for Enterprise users

**URL:** <https://community.auth0.com/t/email-verification-for-enterprise-users/28230>\
**Category:** Get Help\
**Created:** [July 19, 2019, 3:00pm UTC](https://community.auth0.com/t/email-verification-for-enterprise-users/28230 "2019-07-19T15:00:28Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![markd](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/markd/32/38919_2.png) [@markd](https://community.auth0.com/u/markd)\
**Post date:** [July 19, 2019, 3:00pm UTC](https://community.auth0.com/t/email-verification-for-enterprise-users/28230/1 "2019-07-19T15:00:28Z")

</div>

I want to bypass email verification for Enterprise users (SAML, G Suite, etc.).

I have a SAML based enterprise connection set up. An example user in this connection has “Pending” status for email verification under their email address in the management console.

 ![16](https://global.discourse-cdn.com/auth0/original/2X/8/89f5457a54241bd9279f2438413e076277d6d775.png)

If I try to manually set `email_verified` to `true` via the Management API, I get:

```auto
{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "Email verification is not supported for enterprise users",
  "errorCode": "operation_not_supported"
}

```

Does this mean email verification is not applicable to enterprise connections (in which case the Management Console UI should not show a status at all)? Or does it mean email verification is required for enterprise connections **and** there is no way to manually set `email_verified` to `true` meaning no way to bypass this step?

---

<div class="post-metadata">

**Author:** ![markd](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/markd/32/38919_2.png) [@markd](https://community.auth0.com/u/markd)\
**Post date:** [July 19, 2019, 4:32pm UTC](https://community.auth0.com/t/email-verification-for-enterprise-users/28230/2 "2019-07-19T16:32:40Z")

</div>

Addendum: If I log in via my Google Apps / G Suite connection, the resulting profile has `"email_verified": true`. Logging in via the SAML connected IdP, there is no `email_verified` field in the resulting profile, and in the console it shows ‘pending’ status.

Just spit-balling but maybe this is related to G Suite using OIDC and the other connection being SAML? But this just further confuses the 400 error above… clearly email verification is supported in some sense for G Suite enterprise users.

---

<div class="post-metadata">

**Author:** ![mcrawshaw](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/mcrawshaw/32/11400_2.png) [@mcrawshaw](https://community.auth0.com/u/mcrawshaw)\
**Post date:** [August 22, 2019, 6:44am UTC](https://community.auth0.com/t/email-verification-for-enterprise-users/28230/3 "2019-08-22T06:44:20Z")

</div>

I have the same issue. And yes, our G Suite works, and an Okta (SAML) connection does not. Should I be asking for some additional information to be provided from the Okta side maybe?

We don’t want verification emails to be sent to enterprise customers. How do we overcome this?

Mark.

---

<div class="post-metadata">

**Author:** ![markd](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/markd/32/38919_2.png) [@markd](https://community.auth0.com/u/markd)\
**Post date:** [August 22, 2019, 1:22pm UTC](https://community.auth0.com/t/email-verification-for-enterprise-users/28230/4 "2019-08-22T13:22:16Z")

</div>

Hello @mcrawshaw,

Welcome to the Community! If the identity provider is an OIDC provider (e.g., Google), you should get `email_verified` in the security token from the provider. If it is a SAML provider, you have a couple options:

1. Have the provider add an `email_verified` claim to the SAML assertion,
2. Map some other value to `email_verified`.

We went with the second option. From what I can tell, because `email_verified` is a boolean, you can map any [truthy value](https://www.sitepoint.com/javascript-truthy-falsy/) to it. For example, we are mapping the `nameidentifier` field to `email_verified`:

```auto
{
    "user_id": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier",
    "email": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier",
    "email_verified": "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier"
}

```

We know our 3rd party provider will always provide a valid `nameidentifier`, which in this case happens to be the user’s email address, so by mapping that string to `email_verified`, we get `email_verified` set to `true` at account creation time. I am submitting feedback to Auth0 to allow us to edit `email_verified` for Enterprise users.

---

<div class="post-metadata">

**Author:** ![Saltuk](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/saltuk/32/14364_2.png) [@Saltuk](https://community.auth0.com/u/Saltuk)\
**Post date:** [August 28, 2020, 1:39pm UTC](https://community.auth0.com/t/email-verification-for-enterprise-users/28230/5 "2020-08-28T13:39:05Z")

</div>

Hi @markd interesting idea. Though, it might work today, I have some concerns if Auth0 does some form of type checking for SAML mappings in the future. At that point, this may become a breaking change.

> I am submitting feedback to Auth0 to allow us to edit `email_verified` for Enterprise users.

I think it should be a builtin feature on the connection configuration. I agree with this one.

---

<div class="post-metadata">

**Author:** ![markd](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/markd/32/38919_2.png) [@markd](https://community.auth0.com/u/markd)\
**Post date:** [August 28, 2020, 1:53pm UTC](https://community.auth0.com/t/email-verification-for-enterprise-users/28230/6 "2020-08-28T13:53:22Z")

</div>

Worth noting that the Azure AD connection type has an “always set `email_verified:true`” option built in. Just need to see that added to SAML, and other non-OIDC cxn types.

---

<div class="post-metadata">

**Author:** ![sliao](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/sliao/32/25479_2.png) [@sliao](https://community.auth0.com/u/sliao)\
**Post date:** [March 9, 2021, 7:42pm UTC](https://community.auth0.com/t/email-verification-for-enterprise-users/28230/7 "2021-03-09T19:42:43Z")

</div>

Thanks for chiming in w/ agreement for the need for this feature (having a setting to edit email\_verified for Enterprise users w/ SAML connection) to be builtin, Saltuk. Do you know the status of this? I know there’s the 4/30 deadline for migration to having email\_verified set on the connection level, but I don’t see a way to reliably do this.

---

<div class="post-metadata">

**Author:** ![Saltuk](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/saltuk/32/14364_2.png) [@Saltuk](https://community.auth0.com/u/Saltuk)\
**Post date:** [March 11, 2021, 11:08am UTC](https://community.auth0.com/t/email-verification-for-enterprise-users/28230/8 "2021-03-11T11:08:18Z")

</div>

Hi @sliao it is in our backlog but we don’t have an ETA. I don’t think we will have anything before 4/30 unfortunately.

---

<div class="post-metadata">

**Author:** ![ton](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ton/32/12811_2.png) [@ton](https://community.auth0.com/u/ton)\
**Post date:** [May 11, 2021, 3:23am UTC](https://community.auth0.com/t/email-verification-for-enterprise-users/28230/9 "2021-05-11T03:23:06Z")

</div>

@Saltuk Can I confirm there is still no way to set email\_verified to true for SAML provider?

If so, does this mean Force Email Verification rule + Verication Email (magic link) will not work for SAML provider?

---

<div class="post-metadata">

**Author:** ![Saltuk](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/saltuk/32/14364_2.png) [@Saltuk](https://community.auth0.com/u/Saltuk)\
**Post date:** [May 25, 2021, 2:38pm UTC](https://community.auth0.com/t/email-verification-for-enterprise-users/28230/10 "2021-05-25T14:38:06Z")

</div>

Hi @ton, not yet, unfortunately.

> If so, does this mean Force Email Verification rule + Verication Email (magic link) will not work for SAML provider?

You may enable account linking and link users from the SAML connection with an Auth0 DB for the same email address after verifying the email for the [Auth0 DB](https://auth0.com/docs/connections/database) connection. Here are the steps.

1- [Create the user with the management API](https://auth0.com/docs/api/management/v2#!/Users/post_users) on the Auth0 DB with **verify\_email** set to true and **email\_verified** set to false with long (e.g. 20 characters or more) random password. This call should send an email verification link to the user. Obviously, the random password should be different for each user created.  
2- The user clicks the link and verifies the email address on the Auth0 DB.  
3- Finally, perform account linking. There are a couple of ways to link accounts, so I’m skipping the details. You may find the related link [here](https://auth0.com/docs/users/user-account-linking).

Please note that I assume for the SAML connection, your users’ email addresses are verified and belong to the same users you are linking with the Auth0 DB; otherwise, this may cause a security issue for you.

---

<div class="post-metadata">

**Author:** ![ton](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ton/32/12811_2.png) [@ton](https://community.auth0.com/u/ton)\
**Post date:** [May 26, 2021, 3:28am UTC](https://community.auth0.com/t/email-verification-for-enterprise-users/28230/11 "2021-05-26T03:28:38Z")

</div>

Thanks. Yes, all SAML connection users are verified.

---

<div class="post-metadata">

**Author:** ![hassan](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/hassan/32/29698_2.png) [@hassan](https://community.auth0.com/u/hassan)\
**Post date:** [May 29, 2021, 9:38pm UTC](https://community.auth0.com/t/email-verification-for-enterprise-users/28230/12 "2021-05-29T21:38:40Z")

</div>

Hi @Saltuk,  
We also have the same scenario where users are being authenticated through some enterprise connection e.g Open ID. But for those users (when created on Auth0), `email_verified` field is `false`. If we can handle this in rules pipeline, that would be great! If not then I think this scenario should’ve been handled or there should be some cleaner way to do it.

---

<div class="post-metadata">

**Author:** ![Saltuk](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/saltuk/32/14364_2.png) [@Saltuk](https://community.auth0.com/u/Saltuk)\
**Post date:** [May 30, 2021, 8:09am UTC](https://community.auth0.com/t/email-verification-for-enterprise-users/28230/13 "2021-05-30T08:09:45Z")

</div>

Hi, @hassan what was your business use case? Do you need to verify the emails of the enterprise connection users?

---

<div class="post-metadata">

**Author:** ![hassan](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/hassan/32/29698_2.png) [@hassan](https://community.auth0.com/u/hassan)\
**Post date:** [May 31, 2021, 9:42am UTC](https://community.auth0.com/t/email-verification-for-enterprise-users/28230/14 "2021-05-31T09:42:06Z")

</div>

@Saltuk Yes! We need to verify users coming from enterprise connections and we don’t want to proceed another email verification process, we consider all the users coming from enterprise connections as verified users.

---

<div class="post-metadata">

**Author:** ![markd](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/markd/32/38919_2.png) [@markd](https://community.auth0.com/u/markd)\
**Post date:** [May 31, 2021, 1:29pm UTC](https://community.auth0.com/t/email-verification-for-enterprise-users/28230/15 "2021-05-31T13:29:59Z")

</div>

IMO this is a pretty common use case:

1. Auth0 customers want an `email_verified` flag in the Auth0 user profile no matter where that user came from / how that profile was created,
2. For Auth0 user profiles created from enterprise connections, Auth0 customers want `email_verified` automatically set to `true`, under the assumption that the customer already has a trust relationship with the source of the data.

While `email_verified` is an OIDC thing, having it consistently set the Auth0 profile no matter the source of the user profile simplifies the login flow. E.g., no need to give special consideration to enterprise connections in a Rule that happens to check the state of `email_verified`.

---

<div class="post-metadata">

**Author:** ![hassan](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/hassan/32/29698_2.png) [@hassan](https://community.auth0.com/u/hassan)\
**Post date:** [May 31, 2021, 6:43pm UTC](https://community.auth0.com/t/email-verification-for-enterprise-users/28230/16 "2021-05-31T18:43:03Z")

</div>

Got it! In that case data would seem to be inconsistent (even with working functionality), as for enterprise connection users, Auth0 will be showing `pending` as a status for the `email_verified` field.

---

<div class="post-metadata">

**Author:** ![simone.chiorazzo](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/simone.chiorazzo/32/24469_2.png) [@simone.chiorazzo](https://community.auth0.com/u/simone.chiorazzo)\
**Post date:** [September 1, 2021, 3:59pm UTC](https://community.auth0.com/t/email-verification-for-enterprise-users/28230/17 "2021-09-01T15:59:30Z")

</div>

Hi,

we have the same use case. We want avoid email verification for enterprise customers.

Since the last message, is there any new way to accomplish this work without mapping the email\_verified or setting a “fake” mapping for it?

---

<div class="post-metadata">

**Author:** ![markd](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/markd/32/38919_2.png) [@markd](https://community.auth0.com/u/markd)\
**Post date:** [October 20, 2021, 3:24pm UTC](https://community.auth0.com/t/email-verification-for-enterprise-users/28230/18 "2021-10-20T15:24:59Z")

</div>

I believe in the current state this really needs to come from the FSSO partner. If they are connected using OIDC then this should just be included since `email_verified` is a standard OIDC claim, but the partner still needs to provide it.

For SAML partners I believe they need to include an equivalent claim in their security token that you can map to `email_verified` when the user first authenticates.

---

<div class="post-metadata">

**Author:** ![joseph.puthur](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/joseph.puthur/32/33352_2.png) [@joseph.puthur](https://community.auth0.com/u/joseph.puthur)\
**Post date:** [June 9, 2022, 8:49am UTC](https://community.auth0.com/t/email-verification-for-enterprise-users/28230/19 "2022-06-09T08:49:00Z")

</div>

@Saltuk / @markd

Do we have an update here. We have enterprise connections (SAML) users who are marked as email\_verified=false and there is no way to mark them as true. Could the fix be prioritized ?

---

<div class="post-metadata">

**Author:** ![asahyouni](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/asahyouni/32/42536_2.png) [@asahyouni](https://community.auth0.com/u/asahyouni)\
**Post date:** [January 11, 2023, 3:42pm UTC](https://community.auth0.com/t/email-verification-for-enterprise-users/28230/20 "2023-01-11T15:42:31Z")

</div>

Bump. This is terrible. When will this be fixed? Azure AD Connection has a “Automatically set email to be verified” option, why has this not been extended to SAML?

[Next page](https://community.auth0.com/t/email-verification-for-enterprise-users/28230.md?page=2)
