- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
11-18-2025 12:29 PM
I need to manage AD users in Domain B from Domain A. There is no trust between the domains, there is a firewall in the way and they do not share a DNS.
Obviously NTLM is the only option as Kerberos will fail and LDAPs will need to be used - but has anyone configured this using the Microsoft Windows Domain via LDAP platform?
https://community.cyberark.com/marketplace/s/#a352J000000l0sWQAQ-a392J000001eKOlQAM
I've tested it using host files etc, but am stuck as the second domain DC has a cert that doesn't contain the domain name and fails SChannel verification.
11-18-2025 01:58 PM
Hi @Malcolm Murray
The platform policy you are referring is the right one.
Please modify the host file to use the exact name mentioned ( CN / SAN ) on cert.
Also import the RootCA from Domain B on CPM local root certificate authority store. This will allow CPM to trust DC B’s cert.
In the platform policy UseSSL=Yes
Hope it helps !
11-20-2025 02:29 AM
Thanks @Malhar Vora
I previously had tested all of those suggestions without success. I think the root cause is related to the DNS not containing the various MS required DNS entries. Old method of CPM changing works fine, but of course for security I want it over SSL.
I think my next test is a new DC certificate that has a san of the full domain name, but that relys on the AD team wanting to do that.
11-25-2025 04:21 AM
Hi @Malcolm Murray
Looks like Malhar shared an answer to your question- could you let us know if that solved the issue?
If it did, please mark it as “Select as Best” so others in the community can benefit too.
If the issue is still relevant, I’d recommend opening a support ticket so our team can help you further.
Thanks so much!
Shaked
11-25-2025 06:55 PM
Hi @Malcolm Murray
Okay it seems there is no DNS trust and there might not be SRV records for Domain B for Domain A
Your AD team can help try by creating a private zone for Domain B on Domain A 's DNS.
Hoppe it helps!
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!

