Updating Credentials with an open session doesn't work properly when reconnecting

Hello

Thank you for contacting us regarding this matter.

Yes, this is the expected behavior. If you would like the changes made to the entry to be applied, you can update your settings so that reconnects perform a Full Reconnect.

This will close and reopen the session, rather than simply triggering a standard reconnect.

Let me know if you need any help adjusting the settings.

Best regards,

Hi,
This didn't work. I made the change when I posted previous but didn't need to change my password until today. I changed it earlier and had open sessions. When one locked and I just tried to have it reconnect, it's prompting me for a password.

This is what I changed previously:

If I manually enter my new password it connects fine which shows that RDM was still trying to use an old one. Is there a different setting I need to change?

Hello,

Thank you for your response.

I am not aware of any other settings that would need to be changed. Was the behavior different previously? As my colleagues explained, this appears to be normal behavior; however, I would like to confirm that this is not a bug.

Could you please confirm which version of RDM you are currently using?

Best regards,

I just updated my RDM version the other day so I'm on whatever the latest version is. The behavior was the same before, but it was mentioned that I could fix the behavior by changing that option to Full Reconnect.

What I would expect to happen is that any time I connect, or reconnect, to a session, it should grab the password from my stored credentials and use it to log on. I don't see why anyone would want to to use a stored version of that credential when it can use the actual credential itself. If I have a session to a server open, and I change my password, and then I update the changed password in my RDM credentials, if I reconnect to that same server it should use the new password since I updated it. The fact that it doesn't do that, and uses whatever old password it used when I connected originally, seems like a bug. Why would I want it to use a password that I had already changed to something else?

Hello,

Just to help me reproduce the scenario: you have a connection with a linked credential entry, and you changed the password directly in the credential entry while the session was open?

The reason we cache the password into the opened session is straightforward. The password may have been a resolved value rather than a directly bound one, which is why we hold onto it for the duration of the session. The most obvious example of this is when the session prompts the user for a password and they enter it manually. Most users do not change their password while a session is active, but I understand the use case.

I do clearly see the value in having a more intelligent handling of the password, and I am asking the question because from your perspective the behavior may seem obvious, but from a developer standpoint I need to determine exactly when to re-resolve the password, and that decision carries a number of implications worth thinking through carefully.

Regards

We use different credentials to remote into servers than we use to log into our laptops. I can't change my password unless I'm remoted into a server first.

I remote into a server like usual. I do a Ctrl+Alt+End and change my password just like anything else. I then go into my Credential entry in RDM and update it to my new password. If I then get disconnected from my session, and go to reconnect, instead of using the password that I updated in my Credential entry, it uses the password it used when I first opened the session. This password is now old and doesn't work. It then prompts me to manually enter my password and I enter my new password by hand.

If I completely close the session, and then start a new one, it will use the new password as expected. It's only if I need to reconnect.