Feature Request: Variablize Login Actions Passwords

[eleavings]

I dont't think this is a current feature as far as I can tell. But please do correct me if I'm wrong.

I have many, many stored connections with a great variety of Login Actions. It is a perpetual source of frustration that every time my company forces me to update my password, I have to manually change the passwords stored in Login Actions across dozens of connection.

It seems like this would be the perfect thing to variablize. What I mean is, have a credentiual store build into the app. Then when a password is required in a Login Action, present a dropdown of choices.

If I then set all the login action passwords with variables, i only need to change the password in one location: the credential store. Instead of manually across all the store connections.

This would be a huge frustration reducer and time-saver!

[bgagnon]

Hi eleavings,

That is a feature request.

I have added this thread to a feature request in our product enhancement database for a substitution database for logon actions (expect/send, username/password, scripting). Should a future release of SecureCRT include this feature, notification will be posted here.

If you prefer direct email notification, send an email to support@vandyke.com and include "Feature Request - Forum Thread #13539" in the subject line or use this form from the support page of our website.

I have many, many stored connections with a great variety of Login Actions. It is a perpetual source of frustration that every time my company forces me to update my password, I have to manually change the passwords stored in Login Actions across dozens of connection.

However, you can often perform password changes to Logon Actions in bulk, if by manual above you meant you were changing one at a time.

Here is a forum post where the requirements for bulk changes to be successful are explained.

[eleavings]

Indeed I use the method in the linked post as much as possible. However, it's not very elegant and still is prone to a good deal of manual intervention. Thanks for entering as a feature request. I will keep my fingers crossed for seeing something in a future release!