<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
0D54z00008RMqVXCA1Okta Classic EngineDirectoriesAnswered2024-04-17T09:57:19.000Z2022-11-28T00:39:41.000Z2022-11-29T00:32:46.000Z

lh06n (lh06n) asked a question.

Is internal identity referential still required to feed OKTA

I'm testing OKTA and wondering if it can replace a homemade identity referential containing physical users with their accounts and other organizational informations. Could OKTA provide feature such as duplicate and homonymy entry management?


  • DonF.81354 (Customer)

    If I understand the question correctly, yes, Okta is intended to be a full IDP replacement for tools such as AD, Azure AD, and others, both on premise and in the cloud. You can migrate in users via CSV or import directly from the app (if supported). After that is done, you can leverage the Universal Directory as a means to keep your users standardized, organized, and group all together in a single platform further configuring attributes, application access, sign on and password policies, and much more.

     

    As for identifying those users, you can use a variety of identifying attributes both custom and default. If you could give a little bit better idea on your use case I am sure the Community could assist in answering any further questions. Thanks!

    Expand Post
  • lh06n (lh06n)

    Thank you for your answer. Actually, I have a custom identity referential, our single source of Truth that collects and gathers data from various upstream sources and feeds through api or flat files several downstream usages including IAM components (AD, AAD,...).

    For this referential, we have implemented heavy logics to manage automatically homonymy issues, duplicate entries and all things in order to insure that all individuals (physical people) are well identified and linked to their own attributes (identifiers, emails, department, ...).

     

    Could this layer with all custom developments be replaced by OKTA ?

    Thank you for your help.

    Regards

    Expand Post
    • DonF.81354 (Customer)

      From what I understand from your comments, yes, Okta should be able to replace the majority, if not all, these functions. I think your best bet would be to reach out to Okta support to discuss the features of your custom implementation in greater detail and work to map to features supported by Okta. While Okta has the ability to function as the single Identity Provider for your organization, taking inputs from various HR & productivity applications, as well as provisioning capabilities for pushing to those apps, your specific use case involving custom software may best be addressed by a source more familiar with your current implementation and help to devise a plan to best migrate these functions over in such a way to reduce complexity and investments of time and capital.

       

      Please let me know if you have any further questions or even wish to provider further detail that may assist the community in helping to answer your question. Thanks!

      Expand Post
This question is closed.
Loading
Is internal identity referential still required to feed OKTA