- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
01-21-2026 03:01 AM
Hello everyone
we have environment with segregated AD domain, dedicated IDC, and separate PSM/CPM.
Requirement: implement LDAPS-only (636) communication for AD and configure Identity Connector accordingly.
Request clarification on:
CyberArk considerations / best
01-21-2026 03:27 AM
Normal use of Identity Connector (IDC) for Active Directory involves installing the IDC on a domain-joined server. The IDC communicates with AD using the Machine Identity as it's context, with standard protocols. Configure Active Directory integration | CyberArk | CyberArk Docs. If the domain-joined server and the domain controllers are configured correctly then traffic will go over LDAPS (tcp/636) GC LDAPS (tcp/3269) and Kerberos (tcp/88 udp/88). If the SSL is not configured correctly it will try to fall back to unencrypted LDAP. Install at least one (preferably 2+) IDCs on each Active Directory.
You could change this to make the connection pure LDAP only and enforce LDAP SSL; you would need to remove any IDCs that are installed on domain-joined servers and then install the IDC on standalone servers, and then configure the Active Directory as an LDAP directory. Add LDAP as a directory service | CyberArk Docs.
I would recommend continuing to use the IDCs as AD-joined and work to ensure that unencrypted LDAP is blocked at the Domain Controllers to ensure the traffic is LDAPS only.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

