Allow multiple username and passwords for a login entering (often needed!)

Feature Requests Password Manager
,
1

allow multiple usernames and passwords for a login entering (often needed!) Very often some sites have multiple passwords needed to perform different functions, and the ability to keep memory of past passwords and regenerate them if they expire is essential

2

In Bitwarden, you would accomplish this by creating a separate vault item for each set of login credentials.

3

Thank you for the suggestion is what I am already doing but it is precisely not a solution but a workaround

4

With due respect, the fundamental architecture of Bitwarden is to have a one-to-one correspondence with a different vault item for each distinct set of login credentials. So using Bitwarden as it was intended to be used is the solution.

If there is a valid reason why existing functionality is insufficient, then you will have to describe your use-case in detail and provide some rationale to justify the need for what you’re asking for.

5

The one example (from my past) I can think of was a shopping site that required user/pass for login and then at checkout time required you to enter a separate “checkout PIN”.

Today’s solution would be to use an auto-fill custom field and control-shift-L at the appropriate time.

1 Like
6

This is a super important thing to understand. The vault entry is for the credential (username/password), not the website.

If you have two different credentials they belong in separate vault entries. Beyond just a password, there may also be different TOTP, passkeys, auto-fill custom fields, password histories, etc. associated with them.

1 Like
7

I will certainly try this solution and if it doesn’t work I will try to create a screencast of the situation I find myself in in order to illustrate it better.

But I certainly agree with @DenBesten that multiple passwords may be needed on a website, and consequently the current single password structure on some sites may not be sufficient

Is there a guide for this function by any chance ?

Thanks for the tips anyways

8

Yes, create a custom field for the secondary password. This Document explains how to create them: Auto-fill Custom Fields | Bitwarden Help Center

9

With due respect, the fundamental architecture of Bitwarden is to have a one-to-one correspondence with a different vault item for each distinct set of login credentials. So using Bitwarden as it was intended to be used is the solution.

If there is a valid reason why existing functionality is insufficient, then you will have to describe your use-case in detail and provide some rationale to justify the need for what you’re asking for.

@DenBesten mentioned a type of ‘elevation’ where additional verification is required to perform specific actions with an alternative or additional password associated with the current credential/vault item. In this case additional information might have to be manually synchronized to maintain it as an independent vault item (shared additional autofill fields).

In my case, we use an SSO provider. Usually, I am directed to the SSO provider to sign in; however, specific hosted solutions provide a unique login page and authenticate user credentials in the background. In our particular case, the SSO requires the use of a full email address, while our other solution only accepts the username portion.

In this case, the password is continuously ‘synchronized,’ but two separate login usernames are required. I want to configure Bitwarden to use a default username(login) for most URIs that use the credentials but override the username/password for specific URI filters.

Examples of the frustrations below:

Maintain multiple sets of credentials with distinct URI lists and update each credential during a password change.
Since this does not maintain any correlation between the vault items, it requires manually updating vault items independently by searching or exploring the vault for relevant items and using copy-paste.

This is the least cumbersome daily process, but it is prone to errors as a recurring manual process separated by significant gaps in time.

This also requires additional manual synchronization of any other updates, such as other autofill information.

Maintain multiple sets of credentials as unique vault items with overlapping URI lists.

This requires manually selecting the correct vault item during each login and updating each credential for each password change; however, it does ‘link’ the vault items to all sites, making it less likely the user will forget to update a vault item during a password change. However, it requires manually syncing each vault item.

Use a single credential and manually update the user ID for the site(s) requiring a different username/login. This automatically maintains the vault item’s synchronization but requires daily repetition.

Proposed solution/requirements:

Providing both an AltUsername and AltPassword fields would reduce the cumbersome nature of this use case.

AltPassword should be logged in history, similar to the current password field, allowing for additional authentication.

Both should include URI filters for where they will be used in place of the ‘default’ username/password pair.

The ability to add multiple URI filters to each AltUsername and AltPassword item.

The ability to add multiple AltUsername and AltPassword fields.

These features would allow the user to replace the username and/or password with specific URI subsets. This could resolve DenBesten’s ‘additional verification issue’ and my alternate username issue.

Best regards,

Kevin