Same password, many sites, different username iterations

This is a very common use case in with companies that have 1k+ employees and use some kind of SSO solutions connected with their AD. Over the past 6 years there have been multiple different threads about it both on 1Password Community or other places like Reddit:
- https://www.reddit.com/r/1Password/comments/1635dy1/linking_the_same_password_to_multiple_unique/
- https://www.reddit.com/r/1Password/comments/ci2s1n/entry_with_multiple_usernames/
- https://www.reddit.com/r/1Password/comments/10eecbh/shared_password_across_multiple_login_entries/

There's no doubt this feature could be used by thousands of 1Password users - I guess it's mostly an issue of designing the UI/UX well. But once it's added I'd say it could easily be marketed as one more feature emphasizing why 1Password is a better password manager solution for businesses than alternatives  -  especially in companies which have policies requiring that you change your password frequently, so that you won't need to update each login entry's password separately.

I'll pile on to this request as well.  We have AD logins, and there are about 4 different username scenarios.  1) firstname.lastname 2) ADdomain.local\firstname.lastname 3) mailto:firstname.lastname@ADdomain.local 4) mailto:firstname.lastname@outsidedomain.com each for a different piece of equipment that takes a different syntax but all using the same AD password.  It would be awesome to be able to have a unified password for these situations so that when we change passwords I don't have to keep an outside list of every device using that password.

Thank you for getting back to me @alanshutko.

I can see where you are coming from, I have put in a request with our product team to see if there's a way we can better handle these types of scenarios in a future update.

Let us know if there is anything else we can help with at all.

ref: PB34029771

That works, but it causes other problems. 1p will complain about duplicate passwords and it will be more likely that the items will get out of sync (especially for places that ignore NIST guidelines and enforce password expiration).

Hey @alanshutko,

My recommendation would be to use separate items for each of these. Even if the same password is used. If your logins have different usernames, then it would not be a good idea to combine them into one generic and all encompassing login item as they may not fill well.

Let us know if you have any questions.

We have a similar problem at work. A number of items are tied to Active Directory authentication. However, they use different versions of usernames. Some use DOMAIN\username, others mailto:username@domain. But since they are in AD, they all have the same password.

Thank you for getting back to us @AlbertoP.

Please let us know if there is anything else we can help with at all.

Hi Joy_1P,
I had already applied you first suggestion to group the entries with the same credential into one entry with multiple URLs and this reduced drastically the number of entries (very usefull the possibility to modifity the URL descriptio).
About the multiple update it was an idea but reducing the number of entries the issue is reduced so I can manage it manually.

Thanks for you suggestions.

Bye.

Hey @AlbertoP, there's not a way to change the password for multiple logins at once. Even if the same password is used, 1Password treats all logins as separate entities. Furthermore, if your logins have different user IDs, then it would not be a good idea to combine them into one generic and all encompassing login item. Filling will likely not work well.

For the best security, I recommend using 1Password to change and update your passwords so that they can be secure and unique: https://support.1password.com/generate-website-password. There's also an option to use our password generator to create custom passwords: https://support.1password.com/getting-started-browser/#create-a-custom-password. If you need any help with that, let me know.

Hey @mferrall, sorry that we missed your message. If the websites/services are independent, and are not tied to each other on the backend or via some authentication protocol, it's best to create separate logins for them in 1Password and use different passwords for each one. This is from a security standpoint. 1Password does make it easy to generate, save, and fill unique passwords so that should help.

That said, if you wish to use the same username and password for these websites/services, then you can edit the login that you want to use and add additional URLs to it. 1Password will suggest that login on any websites listed in the login.

For the websites/services that require an email address, that will be more tricky. You can create a separate login to handle those. Please just note that not all websites use the same name or id for the email address field, so the ability to fill with this single login may vary. You can always copy/copy or click/drag your email address from the login to the website if filling doesn't work.

I hope that helps. Let us know if you have any other questions!