<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
0D50Z00008C3jVVSAZOkta Classic EngineLifecycle ManagementAnswered2024-04-30T09:27:24.000Z2016-05-19T22:00:18.000Z2020-08-18T00:44:15.000Z

  • AlanA.28953 (Customer)

    Hi Rocky,

     

    It's normally if Okta detects another account with the same 'firstname' and 'surname' values in either Okta or AD.

     

    Also can you check you have 'Create Users' ticked under 'Directory Integrations' > 'Settings'.

     

    Thanks Alan
    Expand Post
    Selected as Best

  • AlanA.28953 (Customer)

    Hi Rocky,

     

    It's normally if Okta detects another account with the same 'firstname' and 'surname' values in either Okta or AD.

     

    Also can you check you have 'Create Users' ticked under 'Directory Integrations' > 'Settings'.

     

    Thanks Alan
    Expand Post
    Selected as Best

  • c6z23 (c6z23)

    Facing the same issue however I don't see any option to move forward except ignoring this user. I want to create a new account as i am not able to find out any other account with same first name and last name but i cannot do that

  • 5u6h3 (5u6h3)

    I get many of these a week (30,000 ish users total)

     

    You need to create a new account with a first.last3@domain.com type username (stick a number in there somewhere!), but don't activate that user.

     

    Then go back to your import screen, select 'Okta user I specify' for the conflict, and point it to the new user
    Expand Post

  • 6c4y4 (6c4y4)

    For people that continue experiencing this today, my team found out that if the primary email is the same for various users, their username is overriden by that primary email and that causes conflict, since they all are technically the same user.

     

    Use the secondary email instead, and leave the primary email the same as the username. That solved the problem for us.

    Expand Post
This question is closed.
Loading
Why am I receiving "This choice creates a conflict" error?