Connecting to Beyond Trust protected Server (Password inheritance only)

Hello Daniel,

I believe the simplest way in your case would be to leverage credential linking, variables and custom fields. Let me explain with a simple setup.

In short, what you'll need is the following:

• A credential entry where you will enter $CUSTOM_FIELD1$ in the username field, and the password you need to use in the password field, as you say it's the same on all your machines.
• Your session entry, where it links to the credential you created previously. This session entry needs to have its username configured in the first custom field, so the variable resolves properly

With this simple setup, you will only need one credential entry with the password, rather than entering that password on every BeyondTrust entry. The BeyondTrust entries will still need to have their usernames entered in their custom field, but assuming they're all different, there's not much to do here. Additionally, you can rename custom fields so their purpose is clearer.

Here's a few screen captures to illustrate the setup I described. Please note I used an RDP entry as the session but it should work with BeyondTrust entries as well.

The credential entry configuration:

The RDP (or BeyondTrust in your case) configuration:

And then, if I try to view the credentials on my RDP entry:

As you can see, the username is correctly the same value as the custom field of the RDP entry, and the password is the one that was configured in the credential entry.

I believe with this configuration, it should help you achieve what you need. Let me know if this helps.

Regards,