topic Re: LDAP integration with Dynatrace Managed Cluster (Configuration Help) in Dynatrace Managed Q&A

Help with configuration for LDAP integration with Dynatrace Managed Cluster

HuseynNajafli — Mon, 05 Jan 2026 12:39:40 GMT

Hello, my question is regarding the integration of LDAP with Dynatrace.
I encounter an error while configuring LDAP in Dynatrace.
I have created an Organizational Unit (OU) named "Dynatrace" in Active Directory, and under it, I’ve created two groups. I’ve also added users to both groups.

Here is the full process I followed:

The connection with Active Directory is successful.
There is no issue with the group queries — the groups are found.
The issue arises with the user queries. Although there are 10 users under the OU, only one user is detected — the one that I used for the LDAP connection setup in Dynatrace.
When I create additional users, they are not able to log in; authentication fails.

How can I properly configure this?
I haven't been able to find any comprehensive tutorials or documentation regarding this. The resources I’ve come across only cover the basics, which I’m already familiar with.

I would appreciate your help.
Thank you.

Re: LDAP integration with Dynatrace Managed Cluster (Configuration Help)

rastislav_danis — Mon, 01 Sep 2025 11:46:01 GMT

Check if your groups and users are properly matched: https://docs.dynatrace.com/managed/shortlink/managed-ldap#matching-users-and-groups

Re: LDAP integration with Dynatrace Managed Cluster (Configuration Help)

HuseynNajafli — Mon, 01 Sep 2025 12:05:28 GMT

I’ve already tested it, but Dynatrace still doesn’t fetch the users properly.
It doesn’t retrieve all the users from the groups located within the OU.
I’ve created groups and assigned members, and my goal is for these group members to be able to log into Dynatrace using their domain accounts.
However, neither the users nor the groups are being detected automatically. (The group is only recognized when I manually enter its name in Dynatrace, and only if it exists in AD.)
Moreover, login still fails — authentication doesn’t go through.

Is there any clear guide on how to configure this properly?
Dynatrace’s official documentation is mostly theoretical — there’s no practical guidance or troubleshooting support for these kinds of issues.

Re: LDAP integration with Dynatrace Managed Cluster (Configuration Help)

rastislav_danis — Mon, 01 Sep 2025 12:23:30 GMT

I had configured LDAP authentication many times in managed and only used linked doc as help. Have you created Dynatrace groups and assign them to proper AD groups?

Re: LDAP integration with Dynatrace Managed Cluster (Configuration Help)

HuseynNajafli — Mon, 01 Sep 2025 12:35:09 GMT

LDAP_Configuration_Image

You can view the configuration here. When testing the connection, it only detects the user directly under the OU, but it doesn't find any of the users who are members of the groups.

Re: LDAP integration with Dynatrace Managed Cluster (Configuration Help)

rastislav_danis — Mon, 01 Sep 2025 13:02:01 GMT

If your group/users queries return required number of items, check this group config and check if LDAP group is properly matched to Dynatrace group. In my example pic, AD group with name "Dynatrace Users" is properly mapped to Dynatrace group "Users" - see yellow labeled message.

Re: LDAP integration with Dynatrace Managed Cluster (Configuration Help)

HuseynNajafli — Mon, 01 Sep 2025 13:42:20 GMT

Yes, I’m experiencing the same result. In Dynatrace, users are simply not being assigned to their respective groups.
For example, I have a group in Active Directory called dynadeveloper, and the user hnajafli is a member of that group.
However, when hnajafli appears in the users list in Dynatrace, it shows that the user is not assigned to any group at all.

Re: LDAP integration with Dynatrace Managed Cluster (Configuration Help)

rastislav_danis — Tue, 02 Sep 2025 05:45:14 GMT

Check your group in Dynatrace if it's mapped to AD group.

Re: LDAP integration with Dynatrace Managed Cluster (Configuration Help)

HuseynNajafli — Wed, 03 Sep 2025 08:45:51 GMT

The issue was caused by an incorrect attribute. I had used member instead of members. After correcting the attribute, the problem was resolved.