Pleasant Password Server Account Cannot Be Verified
Today was that special day when my domain password was to be retired, and I was required to create a new password. I updated my password in the Pleasant Password Keepass, however none of my connections work within RDM. When I go connection setting and click on the link of the password entry RDM saysint that the account cannot be verified. I have verified that the change was also seen by the Pleasant Password Site, which pulls the entry straight from our Pleasant Password SQL Database.
Any Ideas on why my Pleasant Password Account cannot be verified?
All Comments (5)
Hi Derrell,
Of what I know about Pleasant Password Keepass, is it's a Keepass but specific with Pleasant Password.
If you open your Keepass and verify the account (with a copy Username and Password) does the credentials show are good?
If this work fine, in RDM what version of RDM are you using?
And which entry are you using? Keepass or Pleasant Password?
Both of them should work but connect to different system.
Best regards,
David Grandolfo
the connection is made through the Pleasant Password Entry. this is the error message that is reported:
PassMan.Client.PassManAuthException: The account cannot be verified. ---> System.Net.WebException: The account cannot be verified. ---> System.Net.WebException: The remote server returned an error: (400) Bad Request.
at System.Net.WebClient.UploadDataInternal(Uri address, String method, Byte[] data, WebRequest& request)
at System.Net.WebClient.UploadString(Uri address, String method, String data)
at PassMan.Client.PassManWebClient.UploadString(String address, String method, String data)
--- End of inner exception stack trace ---
at PassMan.Client.PassManWebClient.UploadString(String address, String method, String data)
at PassMan.Client.PassManClient.c42b5914f836ded14534c999c17dcad6b()
--- End of inner exception stack trace ---
at PassMan.Client.PassManClient.c42b5914f836ded14534c999c17dcad6b()
at PassMan.Client.PassManClient.GetDatabaseHierarchy()
at Devolutions.RemoteDesktopManager.Business.PleasantPasswordServerReader.GetDatabaseHierarchy()
The Datasource is a SQL back end that uses integrated security, which Pleasant Password does as well. The account used for both is my domain account, which is working everywhere else but when RDM tries to access Pleasant Password. I have confirmed through the Keepass client and through the Pleasant Password server that I can log in using my domain account.
I had to go to File > My Account Settings > Settings > Pleasant Password Server and then change my password to the new one there. this is odd because I do not remember putting my Password here, and this account did not create the entry. Does RDM auto fill the Pleasant Password Server settings using integrated security?
I also had the User settings for Pleasant password set to RDM vault key that was also using my old password. There were still some connection that were using my RDM private key that I did not get moved over to Pleasant Password as well. I used File > My Account Settings > User Specific Settings List where i could see all the connections using custom settings.
Hi,
Thanks for the follow up and good news that the issue is now solve.
Regarding the File-My Account setting, the entry or RDM doesn't automaticly fill the information there. If you configured the sessino with Use "My Account Settings" option enable, so you have to manually add your credentials information under File -> My Account Settings -> Pleasant Password Server.
Best regards,
David Grandolfo