- 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-06-2020 12:37 PM
Hi All,
I would like to use the PSM_RDP connection component on a non-AD domain/windows Target platform. Specifically I have an ldap Target platform that manages the password of an account through ldap against our identity vault (Not Active Directory). What then happens is our identity management service synchronizes the account/password from the identity vault to active directory. The connection PSM_RDP component needs to allow a connection to our AD domain using the account name, but the fields on the LDAP platform are different then the AD platform, as well as the format of the values. How can I customize a copy of the PSM_RDP connection component to look at the correct fields available on my LDAP platform, containing the correctly formatted values instead of looking for fields that would exist on the windows platform? Thanks in advance
11-06-2020 05:12 PM
Hi
What format and value you are using on rdp connention?
11-08-2020 07:42 AM
Maybe expand your question with some examples, I have no idea what you're asking.
11-10-2020 05:00 AM
Let me try to explain better Bob,
I want to manage the account password that exists in identity store 1 (IDP 1), and be able to click the connect button to connect with the "cloned" account in IDP 2. The account in IDP 1 is synchronized to IDP 2 by our meta-directory software behind the scenes. So when the password of the account is changed by the CPM in IDP 1 the new password is synchronized over to the cloned account in IDP 2.
In our environment IDP 1 is an ldap identity store, IDP 2 is Active Directory. So the fully distinguished account names are different. The challenge I was facing is understanding where the connection component gets the values it uses to make the connection so I can make sure those values are correct for connecting to IDP 2.
I hope this makes the use case more clear.
11-10-2020 08:08 AM
So I was able to get this working following a similar example in the documentation. I added the following:
- PSMRemoteMachine property as an Override User Parameters on the PSM-RDP connection component in the Account platform
- LogonDomain property as an Account property
This gives the appropriate domain name prefilled, and the ability for the admin to target the server they need to connect to.
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!

