Feature Request: Linked Passwords

mybigfriendjo
mybigfriendjo
Community Member

From a bit of searching i learned that voting is not really a publicly viewable thing (a view links following)

https://1password.community/discussion/130385/feature-requests-user-voice-forum-section
https://1password.community/discussion/79419/feature-requests-and-votes-how-and-where
https://1password.community/discussion/117893/vote-on-feature-requests
https://1password.community/discussion/46463/where-can-we-see-the-votes

and in most threads it's also explained why.

Mostly so Users don't get a wrong idea of why more voted on features don't get implemented that might not be technically or financially feasible.

I get that. I don't think it would be that much of an issue and you could even just shut down certain Feature Requests that you know are not feasible. But again - i get that. Not wanting to deal with all that is fair enough.

But on the flip side it's a bit frustrating to find a bunch of topics that express the exact feature that I'd love for myself too and don't seem to be able to weigh in because most of them get closed very quickly so i have to open a new topic to bring the feature up again.

In my case linked passwords - it's been brought up in the past, a few times (again a few choice links here)

https://1password.community/discussion/37562/linked-passwords-items-feature-request
https://1password.community/discussion/comment/597292#Comment_597292
https://1password.community/discussion/comment/56758#Comment_56758
https://1password.community/discussion/59327/linking-passwords-of-different-objects

Regarding the voting thing i think there really should be an option to vote on a Topic - even if it is closed. No need for the counter to be publicly viewable - this can be just for your internal feedback and feature analysis but it would make it much easier and quicker for a user to voice support for something AND with the counter not shown you wouldn't have the issue with User confusion about what Feature is more popular and whatnot.
Have users login to be able to vote so you can weed out / consolidate multiple votes from one user on different topics for the same feature. (i know i surely would vote an all Topics i can find regarding linking passwords :P )

And regarding the linked Logins - the only field that needs synchronization is the password field. And it's also the only field that should be synced as URLs, usernames, etc. might be different depending on the Application.

I'm using 1P at work with my windows account that is involved in multiple different SSO scenarios where usernames are sometimes an email, sometimes with domain / sometimes without, etc.

And with tight company security meaning i have to change multiple different entries for different URLs, Server entries, E-Mail Entries, etc. each month it gets very annoying very quickly.

Not limited to Work and Windows though. Thinking about things like Blizzard and Battle.NET being the same entity and using the same account on 2 different websites / game launchers / ...

Also the Watchtower complaining about password reuse - which i can't really do anything about.

You have a 'Related Items' feature so there is the beginning of linking already. The only thing that i need now is something like a checkbox that says "synchronize password fields of 'related items' after password change".

In other Topics there is also talk of a "Parent" Login and multiple "Child" Logins that would change whenever the Parent is changed.

I don't claim to know how difficult, expensive or disruptive this feature would be. It just seems like you are so close already and are just missing the last small step for it to be perfect ;)

I realize that this post might sound more frustrated than i really am - you have a great product that i enjoy to use. Been with other providers in the past only to stay here because i haven't found anything better yet. So all this is really just to make a great thing even better and me wanting to refuel the talks around Linked Passwords :)


1Password Version: 8.10.7
Extension Version: Not Provided
OS Version: Windows 11
Browser:_ Not Provided
Referrer: forum-search:link passwords

Comments

  • Hello @mybigfriendjo! 👋

    Thank you for the feedback! The threads that you linked to are quite dated and our forum software automatically closes inactive threads after a certain amount of time has passed without any new activity. In general, a thread from a few years ago that hasn't had any activity in years isn't likely to be completely relevant to the latest version of 1Password and it's usually best to start a new thread.

    That being said, thank you for the feedback regarding closed threads and public voting on feature requests. I've passed your comments along to the team for consideration in the future.

    Regarding the feature request for your SSO situation: At the moment the best way to store logins that use the same password is to have a single Login item with multiple website URLs or sections. Then, if the SSO platform that you're using doesn't support the exact same username across services, you could autofill the password and then copy and paste, or drag and drop, the specific username needed from a custom field in the Login item. This would require that you leave the default username field blank and store all of the different usernames in their own individual custom text fields.

    I know that this isn't the most elegant solution and I've passed your request along to our product team so that they can continue to look into improving the state of things for users in this situation. I've forwarded your suggestions regarding linked password fields as well. Thank you for taking the time to provide your feedback.

    -Dave

    ref: PB-33390235
    ref: PB-33390518

  • birchmeier
    birchmeier
    Community Member

    hey @Dave_1P thanks for the reply and @mybigfriendjo thanks for the nice post. This is the same feature I would love. An alternative could be able to be associated usernames with URLs this is where everything is still in one login. If one isn't defined than it uses the default username.

  • @birchmeier

    Thank you for the suggestion! I've passed it along to the Product team as well. 🙂

    -Dave

    ref: PB-33656710

This discussion has been closed.