Hi,
We have all our credential information stored in KeePass. KeePass is connected to RDM. We have a Putty SSH session defined as described below:
When I connect the username is entered but the session holds at the Password: prompt. When I hit the Enter key it gives an authentication error. When I copy and past the password and hit the Enter key authentication succeeds.
I created a work arround by using an after connect event but this should not be needed, right?
Hi,
I will ask JF to reproduce it. In the meantime could you specify which version you use?
David Hervieux
Hi paardekooper,
I cannot reproduce your issue with RDM 10.5.4.0 or RDM 10.9.1.0.
What version of RDM are you running?
If you configure your credential in the session, are you able to establish the connection?
Best regards,
Jeff Dagenais
Hi Jean-François,
I'm using RDM 10.5.4.0. When I configure the credentials in the session, the results are the same. The username is parsed (including the enter key). Some sort of greeting comes back and the prompt "Password:" is there. Nothing happens afterwards.
Although te text being entered behind the password prompt is hidden, nothing is parsed because when I copy and paste the password and hit the enter key, the credentials are excepted.
Best regards,
Jasper Kimmel
Just for a test could you enter the username and password directly in the session instead of using KeePass? I want to check if the problem is related or not to keepass.
David Hervieux
Hi David,
I already did but without any luck. When I take a good look at the greeting which the device is sending back when the username is entered, the greeting contains a line break in the middle of a word. So I conclude that RDM is parsing the password to quickly. It just needs a delay between the username and password. Can this be set?
Hi,
Do you use the after login command?
David Hervieux
Hi,
Currently, as a work arround, I use the after login command to enter the password form me again (I like to be the lazy IT employee).
Hi,
I have assigned this thread to Hubert. He will verify if we can tweak the delay.
David Hervieux
Hello,
I went to look in the code and I saw that it takes the delay from the after login commands. Could you try putting the delay in the after login commands tab a little higher to see if it fixes the issue?
Regards,
Hubert Mireault
Hi Hubert,
I set the delay to 10000ms but still no luck. I also tried this delay with the credentials configured in the session.
Regards,
Jasper
Hi Hubert,
I found out that NOT all SSH sessions in my RDM fail on parsing the password. I have some Linux servers to which I am able to succesfuly logon. These devices don't reply with a message after parsing the username. Maybe this will put you in the right direction in solving this issue.
Additionally I want to inform you that some devices (mostly switches) ask to press a key after entering the username and before entering the password. Is there a way to configure credentials in the RDM session and instruct RDM not to auto logon with them? If so, users will be able to script the login process them selfs.
Hello,
I've not been able to reproduce your issue but I will keep looking.
As for your other question, entries in RDM can have their credentials set to "none" (this is in the "credentials" combobox). This should allow you to not have to specify any username or password, and instead you can use after login commands to fill in the username, press a key, and fill in the password. If you want to store the password in a secure field nonetheless, you could use custom fields http://help.remotedesktopmanager.com/settings_information_customfields.htm
This solution could also be used for a temporary fix to the other issue I believe.
Regards,
Hubert Mireault
Hi Hubert,
Thanks for your reply.
Setting the credentials to none would result in me not being able to use the variables like $password$ and so on.
How nice should it be that the credentials are selected and can be used as variables but are not being used to logon automatically. Maybe a feature request?
Hubert,
By the way. The same occurs when using SSH shell. So it definitly has something to do with the device to which you ar connecting.
If setting up a remote session to my computer will help you, just give me a call.
Regards,
Jasper
Hello,
I will get in touch with David about this, thank you.
You should be able to achieve the same behavior currently with the custom fields. The custom fields can be used with variables ($CUSTOM_FIELD1$, $CUSTOM_FIELD2$, etc), so instead of using the $PASSWORD$ variable, you'd use the custom field variable in which you put your password and username.
Regards,
edited by Hubert Mireault on 6/10/2015
Hubert Mireault