Query Regarding Migrating Active Directory to Microsoft Entra ID

kimjohn
kimjohn
in Active Directory

We have a few queries regarding the Active Directory (AD) setup as Decisions is planned to migrate to the AWS ECS containerization environment and upgrade to version 9.

Here are the questions:

  1. During the migration, we will be using Microsoft Entra ID. Will this impact the current authentication and identity configuration in Decisions (currently hosted on IIS with version 8.20) when moving to the new environment? Are there any limitations or dependencies that need to be flagged during the migration or version upgrade?
  2. Will Active Directory still support NTLM v2 or Kerberos authentication after the migration?


Comments

  • amershaik_Decisions
    amershaik_Decisions

    Here are the suggestions regarding your queries:

    • If you are moving fully to Microsoft Entra ID and discontinuing on-premises Active Directory, LDAP-based authentication will no longer be supported, as LDAP depends on an on-premises directory.
    • In Decisions v9, when running in AWS ECS, users can still log in with their domain credentials. However, this is typically achieved through Entra ID using SAML or OpenID Connect, rather than LDAP.
    • NTLM and Kerberos protocols only apply when a traditional Active Directory domain is still in place. Once the environment transitions fully to Entra ID, these protocols will no longer be applicable.

    For more details on setting up SSO with Microsoft Entra ID, please refer to the official Decisions documentation:

    https://documentation.decisions.com/docs/setting-up-sso-for-entra-id

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Categories