Field References (Ability to set different usernames for different websites using the same password)

Bitwardens main focus seems to be on “casual / browser-only” users. For these people Bitwarden offers a lot of great and useful features, but when it comes to admin / offline operations it’s lacking many many features such as Auto type, SSH Agent Support, this one here and some more. Personally I tried Bitwarden and KeePassXC in parallel but never made the switch to Bitwarden because it’s lacking too many useful features and now I’m not using it at all anymore.

I still watch and vote these topics, hoping the features might be implemented at some day. However, I’m not that optimistic seeing the current focus of the project to introduce a new stuff like the secrets manager.

Especially if the password of an account changes, this must be adjusted on all existing entries. It would be great to have an account entry that can be referenced by other entries. This way, the adjustment would only have to be made in one place and all other entries would always be up-to-date and no entry would be forgotten.

It would be handy if I could create one record and link it to another. Some examples of where this would be useful:

  • If I have a credit card with a bank, a web login for the credit card, and a web login for the bank, it would be convenient to be able to link the records together. E.g., make an “address” record of contact information for the bank, and link that record as the contact information for the other records. Or link from the “credit card” record to its “web login” record.
  • If I have an account where my login is via GitHub or FaceBook or OAUTH2 or OpenID, it would be convenient to be able to link to the web login in question. I use different kinds of 3rd party logins for different kinds of web sites and right now I have to remember which is which.
  • Perhaps it would be handy to have a field allowing a drop-down of 3rd party logins, and to be able to flag different web logins as a 3rd party login to be added to that drop down.
2 Likes

It would be useful for me to know which account (Facebook / Google .etc) I used to log into this site with.

It would be useful to link one record to another, and if the password/TOTP key is updated on, it updates on the other. This is because often I have to input usernames in different formats:

DOMAIN\username
username@domain
username

but they are all authenticated using the same backend. I currently have to maintain 3 records (with identical passwords) to be able to accommodate this, but if I change the password on one, I have to remember to update the password on the other two.

The alternative option would be to allow for multiple usernames in the same record, and allow us to select the username style when filling in the field (or even better, give us the ability to specify on a per-site basis which username to use)

1 Like

I don’t know if this is possible, but having an option to link a login to another login or multiple logins, that share the same username, email and/or password, would be extremely convenient for SSO (Single Sign On). Specifically, changing the password for one login would also change the password for all of the linked logins (same user account).

My company has dozens of web and Android apps that use SSO which means each user uses a single password to access all of them. Most logins use the individual’s username but some use their email address, instead.

When it comes time to change your password (every 30 days), login managers become inconvenient because you have to change the password for every one of your SSO logins. In BW, I know you can add multiple URL’s to each login but only the domain name is displayed in the GUI so you don’t know which launch button to touch. It’s much more convenient to have a separate login for each URL because you can give each one an easily recognizable name.

Maybe take it a step further and give the option to pick which field(s) you want to link so you are not limited to only the password field.

Is this possible as a future feature?

1 Like

Relationship ‘links’ between items

  • Within BitWarden, it would be helpful if you could ‘link’ items together by forming relationships between them, whether they are for reference, or as a dependency.

Feature function

  • What will this feature do differently? Adds the ability for items to be linked together (relationships formed between them) such as a dependency, or, just for reference.
  • What benefits will this feature bring? As a use-case, you may store a Login item in your BitWarden Vault for service that uses a third-party authentication platform (like Google or GitHub). That third-party platform has it’s own separate Login item, but is linked to our new Login item as a dependency. This prevents duplicating data (that can quickly go out of date), and provides the ability to locally keep track of how those logins are being used / what they provide access to.

Example Use Case

I would like to create a reCAPTCHA key for my website and have those details stored securely in my BitWarden Vault:

  1. I login with my Google Account, and create the reCAPTCHA site key/secret appropriately for my website.
  2. I create a Login Item (or Secure Note) in BitWarden to store the reCAPTCHA details using new Hidden fields. Note that the username/password fields are not being used in this case, because we authenticated using our existing Google Account, which has it’s own Item inside BitWarden.
  3. I’d like the ability to create a referential link between these two items in BitWarden. This way, on my reCAPTCHA item, I could link my Google Account as a dependency, so that I know which account it belongs to for future reference.
  4. Viewing either item will show the relationship between them, so that you can easily click and use/view/edit those items appropriately.

I also need this feature. I think I found the request with the most votes, so we should all vote there:

Ditto. Same issue here. We have SSO, that syncs the account to multiple systems. Multiple AD domains, OpenLDAP, Azure AD, etc. Some systems require your username, others your domain\username, and yet others use your UPN, firstname.lastname@domain.com.

I currently have 12 unique credentials in Bitwarden for a single actual account. So when I change the password, like I did today, I have to go update 12 different records in Bitwarden.

I’m sure this is rather common across larger complex enterprise organizations.

I couldn’t agree more !
This would be extremely usefull !

It would be amazing in linking logins with credit cards; to determine which cards are on which accounts, and maybe batch edit them

I’d really appreciate this feature!

Here is my use case:
In my Company we use Microsoft LDAP, so Login with Microsoft is used virtually everywhere. Tho on our internal clocking website and on premise Gitlab we need to sign in with our username, not the Email (ok, I can deal with that using Custom Fields). Tho In Gitlab I also need to have 2FA active, this would collide with Microsofts 2FA code. Cross referencing fields from other accounts would solve this issue.

This feature alone would transform Bitwarden from “just another [good] password manager” to a true power user’s password manager with advanced relational database-like abilities. PLEASE implement this!

I just migrated from keepass and I miss this feature.

I second this, and I also wanted to propose a slightly different solution.

Besides the option to just link fields between separate entries (the KeePassXC method), I suspect most of the use cases for this feature could actually be covered with a much simpler, less disruptive implementation.

Ability to specify different usernames per URI

When specifying multiple URIs for a single entry, add the ability to specify a custom username for each of the URIs as well.

Feature function

  • What will this feature do differently?

Adds the ability to specify different usernames per URI to the same vault item.

  • What benefits will this feature bring?

There are situations where a single user account, with a single password, requires different usernames depending on the platform where the login is being done. Today, we need to have a separate entry for each username. This not only clutters the vault, but also makes it harder to maintain as we need to update the password in every different entry whenever it changes.

Example Use Case

In corporate environments where each employee has a personal account to access all systems company-wide, it’s very common to require different usernames depending on where the login is being done. E.g.: some cloud-based systems may require the full email address (john.doe@company.com), whereas some on-prem systems may require a shorter, local username (john.doe), and others may even require a prefix with the domain the user is logging into (e.g: //ROOT/john.doe).

Today, we need to create a separate entry for each of those usernames, even though the password is common across them. Additionally, corporate environments typically require their employees to update their passwords very frequently, which further exacerbates the problem as it makes it tedious to manually update each of the entries one by one.

A very simple solution could be to add an (optional) setting whenever we add a new URI to an entry, where we can also specify a custom username that’s different from the default username in this entry.

So for a single entry, we could have:

  • Username + password
  • URI 1
  • URI 2 + username 2
  • URI 3 + username 3
  • etc.

For those URIs where no custom username is provided, the default one is used of course.

Hi,
in many enterprice envirnament i use Domain password for access to their application.
An example can be:

  1. Jira
  2. Confluence
  3. Jenkins
  4. Time Table

I can’t group all entry in one because have different note and meaning bat all have same user and password.

For me is more simple if change one entry can change all other, or have a folder with all entry with the same password and change folder password change all entry password.

thx
Saul

Create one item with multiple URLs?

you ask put together banana and apple … ok are all fruit but different thing.
I need to name all item.
For examples:
http://10.0.0.1/ → Jira
http://10.0.0.2/ → jenkins

What name i set?

no I need different entry.

bye
Saul

Just name it “Company Logins”

then click the “New URI” button 3 times and input the 4 URLs.

The whole point of password managers is to use unique passwords on every site, so adding this feature would be counter-productive.

If I call them company login how I select what I want if the url name with ip? Do you think I remember the ip for the link? Or I need to use an other software for open?

Thank’s but one solution cross platform is better.

You say true use different password is a Good practice but not always practicable.
I can’t choose it, because society use windows domain or LDAP for manage credentials.

than I need to find a why to manage their service.