<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
System Status
Announcements
Announcements
Search
Search
Select Language
Knowledge Base
Knowledge Articles
Support Videos ↗
Documentation
Product Documentation ↗
Developer Documentation ↗
Product Release Notes ↗
Community
Events & Webinars
Okta Ideas ↗
Resources
Product Hub
Customer Success Hub
Product Release Update
Learning
Okta Learning ↗
Get Support
Open a Case
HomeCommunityForum
0D54z0000A4gmMqCQIOkta Classic EngineOkta Integration NetworkAnswered2024-04-30T17:47:16.000Z2024-04-15T13:26:00.000Z2024-04-30T17:47:16.000Z

User16802118410658061824 (Customer) asked a question.

April 15, 2024 at 1:26 PM
Published OIDC application doesn't provide email verified field to Auth0 enterprise connection

Hello,

 

We are a cybersecurity company and we offer an integration for our customers that utilize Okta as their identity provider solution to authenticate to our platform using Okta's identities. We are using Auth0 as an identity broker and with their enterprise connection, we set up Okta workforce integration.

 

Recently we published a NetBird application into Okta's integration network, https://www.okta.com/integrations/netbird/, but before that, we recommended our users to follow Auth0's steps to set up a generic Web application as described here: https://auth0.com/docs/authenticate/identity-providers/enterprise-identity-providers/okta.

 

We've noticed that the published application has one difference when integrating it with Auth0 connection with Okta's workforce when we compare it with the generic web application.

 

With the generic application, the new users added to auth0 have the email verified status set to true, but with the new application, they have the status set to false. Is that something that can be corrected?

  • 4 answers
  • 285 views

  • Mihai N. (Okta, Inc.)

    Hi @User16802118410658061824 (Customer)​ ,

    Unfortunately , this situation is outside of the Okta Community purview, but I recommend reaching out again to oin@okta.com as per our documentation.

    In the meantime, you can also look into your submission by logging in to oinmanager.okta.com to see if there's something in the configuration there, that can be corrected/changed. 

     

     

    Regards.

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Expand Post
    Selected as Best

  • Mihai N. (Okta, Inc.)

    Hi @User16802118410658061824 (Customer)​ , Thank you for reaching out to the Okta Community! 

     

    If you are the ISV, please reach out to my colleagues from the Okta Integration Network team via oin@okta.com to discuss the details of the implementation. As far as I can see, there is no configuration option available from that Okta Admin dashboard that would influence the user's email status upon provisioning. This means the option might be hardcoded in the implementation, if at all available from the Okta side. 

    My colleagues should be able to assist you with clarifying the matter. 

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

     

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Expand Post

  • User16802118410658061824 (Customer)

    Just an update, from Auth0 side they mention that they are applying what they receive from Okta and that in this case, the published app is not sending the email_veirified attribute for the user.

    • Mihai N. (Okta, Inc.)

      Hi @User16802118410658061824 (Customer)​ ,

      Unfortunately , this situation is outside of the Okta Community purview, but I recommend reaching out again to oin@okta.com as per our documentation.

      In the meantime, you can also look into your submission by logging in to oinmanager.okta.com to see if there's something in the configuration there, that can be corrected/changed. 

       

       

      Regards.

      --

      Help others in the community by liking or hitting Select as Best if this response helped you.

      Expand Post
      Selected as Best
This question is closed.
Loading
Published OIDC application doesn't provide email verified field to Auth0 enterprise connection