To Whom It May Concern:
I've discovered an issue that I can duplicate with easy regarding the auto filling of credentials in certain situations. This seems to primarily occur when using VMWare vSphere client although I have seen it occur elsewhere as well (can't remember where at the moment though). When I double click on a vSphere connection in RDM it starts the vSphere client, fills in the vSphere credentials, and then initiates the vSphere connection. The problem is that whenever I do this the connection fails due to an incorrect password and/or username. What I have been able to determine is that RDM appears to be truncating a character out of the password when it auto fills it into the vSphere client. I've determined this by copying the password from the vSphere connection in RDM and manually pasting it into the vSphere password field after it fails to connect. The number of asterisks shown in the password field increase by one indicating that RDM is failing to properly auto fill one of the password characters; which one I have no idea. What I can tell you is that the credentials for this connection are stored locally in one of RDM's "Username/Password" type credentials and that the password is 16 characters long. The interesting thing is that if I use a shorter password the issue doesn't seem to occur...
Please let me know if you need any further information. Have a good day!
Do you have any special char like a " or a space?
David Hervieux
Yes sir, I do. I assume this is a problem...? Is this not supported?
Hi,
We invoke the command line and I suspect that it's not handled correctly. Just for a test could you try to es
cape the quote?
http://stackoverflow.com/questions/2403647/how-to-escape-parameter-in-windows-command-line
David Hervieux
No problem. I'll escape that specific character and report back.
Escaping the character fixes the issue. Any chance you guys could implement a fix for this?
Thank you!
Great! Thank you for the test. We will fix it.
David Hervieux