Adding UPN field in the credential object

Hello,

We'll add this to our todo list. It's not a small change since it would require adding a UPN field in a lot of places (not only the username/password entry type), but it's an interesting idea that might simplify workflows.

Out of curiosity, how do you currently work around this lack of feature?

Regards,

We workarounded creating a different credentials object with the same password. Maybe useful also creating a parent child structure for the credential object hereditating the username or password from the parent. Any changes in the parent will apply to the child too.

Thank you for the information.

As far as inheriting credentials, the best way to go about it would be to have a folder that points to the credential, and the entries under it set to the "inherited" credential mode. For more information, you can check out this help topic https://help.remotedesktopmanager.com/bestpractices_credentialmanagementforteams.html

Regards,

Hi,
sorry but probably I was not able to explain my idea. As you already have the sub connection into the session object I'm asking to create the same "link" in the user Object so you can create dependent account information able to refer and use some values from the father object.

Ex.
Main Credential
Username, Domain, Password, Expiration, UPN, etc.

Child Credential

Username, {Domain}, {Password}, Expiration, UPN, Etc.

The field between parenthesis {} are link to the parent account field value. If you change in the Parent the values will automatically change also in the child.

When it comes to subconnections, you could use the $PARENT_*$ variables to achieve this. You can see the list of them if you edit one of your subconnections and click the Variables button:


So for example, you could put the $PARENT_USERNAME$ variable in a field to be able to use the same credential as the parent entry.
Keep in mind that password fields don't support variables, so I'm not sure you could achieve exactly what you want.

Regards,

Hi,
to my knowledge is not actually possible to create a parent/child relationship between credentials object. Just Folder/Credentials. In any case the $PARENT_PASSWORD$ does not exists.

Ah, you're right, my bad. You can do it with session types but not credentials, so I suppose it wouldn't be possible in your scenario.

Regards,

That's why we raised the feature request. Hopefully you will find a way to implement in the future releases.

For now we'll focus on adding the UPN username format and a UPN field.

Regards,

Hi all
interesting question. I think the OP question will be answered if:

1. UPN is added as a field within the credential object ( or: create a new credential object type that also contains an UPN field next to username, domain, password)
2. in Connection objects - Advanced there is a: Username format field, with options: No change / {Domain}\{User} / {User}@{Domain} / {User} and this list would then be extended with that {UPN} field.. Note that the UPN sometimes matches the {User}@{Domain} syntax, but doesn't need to, in our organisation the UPN is NOT equal to {User}@{Domain}
   1. 

Note, option 2. needs to be settable in a number of connection types, don't know how generic this code is.

We already use this in some instances where my admin account needs to be specified with only the {User} name, for instance in some VMWare connections.

Regards, Ben

Hello,

Yep, this is our plan for the changes. 🙂 The dropdown with the username format is available for session entries so it should be pretty much globally available.
As a note, the UPN field will only be available in the Username/Password entry for now.

Regards,

Hello,

This feature has been completed internally and should be available starting from RDM 2020.3.0.0

Regards,