Depending on your organization's security policies, there are multiple ways of handling credentials. We can manage a wide range of scenarios; the most popular are listed below. It is critical to understand that these are the credentials used to connect to remote hosts, not the ones you use to launch Remote Desktop Manager.
Most of these selections do not exist in the Free edition of Remote Desktop Manager as they depend on features offered by an Advanced Data Source.
Below are a few key points that the administrator of the solution must be aware of:
| OPTION | DESCRIPTION |
|---|---|
| Password visibility | You can store passwords in a credentials entry (username/password entry), which, by default, makes the password usable but not visible by the end user. Multiple credentials entry types are provided. It's important to choose the type carefully based on administrative and security needs. |
| Credentials set on folders | Folders can have defined credentials, useful for reusing the same credentials across a branch of the network infrastructure. To use these, child sessions must be adjusted to use inherited credentials. |
| Entry location | Storing entries in the tree view allows users with View permissions on that entry (or folder by inheritance) to use them, enabling credential sharing with team members. A user vault is available for storing personal information privately. These credentials can still be accessed publicly by referencing them or through User Specific Settings. |
| User Specific Settings | User Specific Settings provide partial overrides for entry settings, including credentials. Overrides allow selecting credentials directly or linking to credentials stored elsewhere, like in the user vault. |
Here are the most common scenarios and ways to resolve them. In the majority of cases, we prefer sessions to use inherited credentials, which means they climb the tree until they have access to a set of credentials, whether defined, linked, or overridden in an entry.
| SCENARIO | STRATEGY |
|---|---|
| One set of credentials is used by all of the staff, be it for the whole system or for a branch in your tree view (customer, department, etc.). | Set the credentials on the Vault settings. All children use inherited credentials. |
| Each user has their own credentials for many different branches (often corresponding to customers/departments, etc.). | Make use of the User Specific Settings on each branch. All children use inherited credentials. |
| Each user has its own credentials managed by an administrator. | This solution involves a little more work. The administrator must create a folder for each user, then grant permissions only to that user. The user will then use User Specific Settings to specify that the credentials stored in that folder are used to override what is defined in the entries. |
| Each team uses the same credentials. | As above, but all team members have access to the folder. They all have to use the User Specific Settings. |
| Each user uses their domain account. | Configure sessions to use My Personal Credentials. Each user will be prompted to define them once per workstation that they use. |