Private Vault Credentials applied at folde level
Hi
Ver: 10.6.7.0 Enterprise
Im having issue with private vault credentials working on RDP sessions when the credentials have been applied using 'user specific settings' on a parent folder.
If I configure user specific settings directly on a RDP session (Server A) they work flawlessly, but if I apply the same user specific setting to the parent folder containing Server A, then I am prompted foo credentials.
As a bit of background I started off on ver 10.1.??? and everything worked as expected. As I'm in the process of configuring the application, I have been "looking" at a lot of settings and types of remote connections.
Upgrading to 10.6.7.0 resolved the problem, but only temporarily. I have two accounts on my desktop, my primary normal user account that I intend to run RDM with and my administrator account that is an admin on my laptop and the servers in the same Active Directory domain. My intention is to use my Admin account to administer the application from the root folder level and my normal users account for day to day use.
Following the upgrade to 10.6.7.0 here is what happened.
Ran the application as a normal user - everything worked.
Closed RDM
Ran RDM as an Admin
Closed RDM
Ran RDM as a normal user - This is when the private vault credentials stopped working again at the folder level.
Please help
All Comments (2)
Ok, I got this fixed by changing the credential type on the RDP sessions to "Inherited".
What Im not clear on is
a) Why the credential type "default" worked on sometimes and failed sometimes.
b) What the expected behaviour of "default" is?
Hello,
When default is used, it allows you to specify credentials directly in the session.
You may have been impacted by the presence of credentials for that device in the Windows Credential Manager. RDP will simply use them if present. We make use of that ourselves under certain conditions.
Maurice