$PARENT_PASSWORD$
Version: 8.0.12.0 Enterprise
I have a "Host" session type with the Advanced "Allow password in variable" set.
I then create sub-connections under this. I have a ssh (putty) and VMWare Virtual Infrastructure Client both of which can auto-login with password entries. In each sub-connection the $PARENT_HOST$, $PARENT_DOMAIN$, and $PARENT_USERNAME$ all work great. However, when I put $PARENT_PASSWORD$ in the password field and also check the "Allow password in variable" in the advanced tab of the sub-connection, and then try the sub-connections they both don't work and its clear from the VMWare Login Dialog that the number of masked characters is the same number of characters in the string "$PARENT_PASSWORD$".
If I type the password directly into the sub-connection password fields they both work as expected. It looks to me like $PARENT_PASSWORD$ is not honored. Actually it looks like the password field on the sub-connection doesn't do any variable substitutions as $PARENT_USERNAME$ or anything else in the password field also gets sent literally w/o replacement.
Note I have tried unchecking the "Allow password in variable" on both the parent and the sub-connection and there is no difference. They don't seem to do anything.
All Comments (4)
Hi,
This is not a bug. Instead of using the variable, you should select in the Credential field: Parent. This will inherit directly the username/password from the parent.
RDM is unable to replace a variable in the password field.
David Hervieux
Thanks.
David,
I am replying mostly to aide others learning to use RDM.
Is it fair to say that:
RDM supports Credentials entries, and when possible they should always be used as the proper format for saving a username/domain/password. For example, instead of filling in a username and password field on a host entry if you see no need to reference an external credential, you should instead use an embedded credential vs. typing the username/password into the host entry. This way if sub-connections are created, they can use the "parent" credential reference.
I think what is confusing is that the system on a lot of session types has a place for username/password but there is also an embedded credential. Since you can't use variables in password fields, the only way sub-connections could get a password from the parent is via using Credentials at the parent level.
The $USERNAME$, $PASSWORD$, $PARENT_USERNAME$, $PARENT_PASSWORD$ variables are not intended for use in username and password fields within the various session types. They are intended for use in macros, scripts, command lines instead.
If this isn't correct, could you clarify further? I think many users would benefit from having a type of best practice recommendation, especially when just getting started with RDM. What makes RDM great is all the flexibility in configuration, but it is also what can make it confusing as there can be multiple ways to do something and it appears that each way is there for a specific use case and there is usually a right way to do various things, but it isn't clear what that is until you have many hours of use into the system. This may only be true when trying to use templates and sub-connections extensively, which is what we are doing, but it may impact simpler uses as well.
Thanks,
Brett
Hi Brett,
I really like your comments and this clarify a lot. I will add your comments in our online help. We are also planing a new topic with some best practice and a technical use case as well.
David Hervieux