Feature Request: Linked Accounts

Haravikk

<div class="IPBDescription">Multiple URLs for one Login, Equivalent Domains, Domain Aliases, etc.</div>One feature I've either missed, or that might be nice in future, is the ability to associate multiple domains with a single log-in entry. In my case I own multiple domains, however each hosts a stats readout (I believe a lot of web-hosting companies do this); it of course has a single log-in, but because of the multiple domains 1Password doesn't like it so much, but I'd rather avoid having entries for each one as I'd need to update them all if I change the password.



A bit of a specialised example I know, but some site-networks that use shared logins across the sites may run afoul in this way too. It's not a huge inconvenience, but to be able to have a log-in entry that covers multiple domains, or link multiple entries together somehow, would be neat, and possibly useful for some other cases as well, such as multiple sites under a single domain that use the same details, but with different form-layouts (secondlife.com is the biggest example of this I know of).

dteare

[quote name='Haravikk']One feature I've either missed, or that might be nice in future, is the ability to associate multiple domains with a single log-in entry.[/QUOTE]



We are very close to adding the ability to associate domains and allow you to define them as "equivalent". For example, Logins saved for hotmail.com should be usable on live.com since they are indeed the same site. I hope this feature will see the light of day soon :)

kevinashworth

+1

RobYoder

[quote name='dteare']I hope this feature will see the light of day soon :)[/QUOTE]



Me too!

Perceptes

Any update on this feature? I'd be really useful for me now that Steam is on the Mac, because the store is at steampowered.com, but the community site is steamcommunity.com and they both use the same account.

Nik

Sorry, Perceptes, there's no update on this feature just yet.

fiokins

For what it's worth +1 for this, I'm the victim of LDAP everywhere for pretty much every intranet site at my company; I don't really enjoy updating ~30 logins whenever they decide to force arbitrary password changes on me!

MartyS

Thanks for letting us know it would be helpful to you, and welcome to the forums, fiokins!

Matt B

[quote name='dteare']We are very close to adding the ability to associate domains and allow you to define them as "equivalent". For example, Logins saved for hotmail.com should be usable on live.com since they are indeed the same site. I hope this feature will see the light of day soon :)[/QUOTE]



Oh, how marvelous this would be. I just purchased 1Password and was disappointed to see that it's not (yet) supported. I'm glad to see that something is in the works; I hope you're able to release it soon!

maik.tailor

Yes! Now, I have to duplicate the entries for each login - and I have alot 1:1 copies of my webpages on my local machine..



thx :)

bigethan

I need this feature. Another LDAP at work person here, forced to change password every 90 days. Sadly, without this ability, it's easier to just not use 1password.

macpug

majost, maik.tailor, and bigethan: welcome to the forums! Hang in there with us, hopefully it won't be too much longer. I understand how frustrating it is to have to change the password every 90 days...I had to do that for nearly 5 years. I was forever forgetting my password!! Thanks for your support (and patience ;) )

bigethan

I'm guessing you had to do it for five years before there was this crazy software called 1password that managed all your logins. Now that 1password exists my expectations have changed :-)



Thanks in advance for any information you can provide on the status of this feature.

macpug

bigethan: absolutely!! Once 1P came along, everything changed for the better. We'll keep you updated as we know something. Cheers ;)

Nik

[quote name='bigethan']Thanks in advance for any information you can provide on the status of this feature.[/QUOTE]

We've made some progress on this. For example, 1Password understands that agile.ws and agilewebsolutions.com are the same. What we need to do to complete this feature is add an interface that would enable you to add your own domain aliases. I don't have a timeframe for when that will happen, but it's on our radar.

Haravikk

When you say that it detects they are the same, is this because when you log-in with your details it recognises that you've used the same details for agile.ws as you did for agilewebsolutions.com and offers to automatically link them? Being able to do it manually is of course awesome, but automatic detection will be most sweet :)

Nik

[quote name='Haravikk']When you say that it detects they are the same, is this because when you log-in with your details it recognises that you've used the same details for agile.ws as you did for agilewebsolutions.com and offers to automatically link them? Being able to do it manually is of course awesome, but automatic detection will be most sweet :)[/QUOTE]

That would be very cool, but 1Password doesn't have this sort of detection. Right now it's just been hard-coded, meaning 1Password has been told that domain A and domain B are the same.

bigethan

Man, why you gotta tease like that :-) It's clearly a feature your devs wanted enough to hack into their own sites, but us paying customers don't rate enough to get a little bit of interface so that we can use it too.



As a bit of user feedback, when I first ran into this I went into 1password thinking that I could add multiple domains / urls to an entry. Was surprised I couldn't, and headed here.



Autodetection would be cool too: "Do you want to save this login or, alternately, add it to '[List of Matching Login Accounts]'?

MartyS

We'd kind of like to have an interface to it too but the facility needs some help internally. We've cobbled it together just enough to work in a limited number of cases. I'm sorry that it's not something that we can provide today (or even "tomorrow").

bigethan

What does ""tomorrow"" mean? Because I'd happily take it a week from now. But if it's gonna be more than a year before the functionality is complete, then I'll just deal with it. That's the crux of the issue - should I wait bit to save myself some work, or will I be waiting for a long time and getting more and more frustrated as I wait.



Thus far what I've heard is that: there's a version that works for a couple sites, but it won't be ready "tomorrow"



I'm not as annoyed as this message sounds, just trying to get a decent answer.

MartyS

[quote name='bigethan']What does ""tomorrow"" mean? Because I'd happily take it a week from now. But if it's gonna be more than a year before the functionality is complete, then I'll just deal with it. That's the crux of the issue - should I wait bit to save myself some work, or will I be waiting for a long time and getting more and more frustrated as I wait.



Thus far what I've heard is that: there's a version that works for a couple sites, but it won't be ready "tomorrow"



I'm not as annoyed as this message sounds, just trying to get a decent answer.[/QUOTE]



That's fair to ask, but of course you probably already know that we cannot give a feature or bug fix release date for any of our products. If we were to 'slip' even for the best of reasons our customers would be disappointed.



This capability is not something that you'll see extended to the user interface in the next several months. While it would be helpful -- we're in agreement there -- it does have a workaround which is to maintain additional Logins. Many features that we also agree need to be provided have no such workaround and we try to get those into your hands first... and there are boatloads of those features waiting to be implemented. Will this one be available to you in a week? No. Within a year? I honestly don't know. But we do know that it would help some customers greatly and it's something that we want to do.

Spaceman

I too would like this. At work, they are migrating several of our services (time cards, employee records, training request) to use a common UserID and Password although they are each on separate sites.



I have a suggestion (which may be dumb but I throw it out there ;-).



What if you could create a login entry like you do now, but not put in any domain info. We'll call this entry 'Master'.



Then, for each of the various sites that use common UserID and Password you create their own Login items just like you do today, however, instead of actually putting in a UserID and Password, you (Agile) provide some kind of link that actually reads the UserID and Password from the 'Master' file created above. It would be something similar to an 'Alias' on the Mac or a Cell 'Reference' similar to Excel.



So, when you want to log into your 'Time Card' site (as an example), the ID and Password fields in the 'Time Card' login screen don't actually contain this information but contain something like '<Master>' that would pull that info from the 'Master' login entry.



This seems like it would be easier than trying to take one entry and associating it with multiple domains.



What do you think?



Regards,



Spaceman

[Deleted User]

Hi Spaceman,



I like it, it certainly makes a lot of sense when you think about it, having a saved login for domain.com that you can then reference the details for from a login for tpsreports.domain.com or redstapler.domain.com (sorry, had to get an Office Space joke in). I'm not sure how easy this is going to be to implement, but I'll add it to the virtual ideas board (the one disadvantage of not having an actual company office, no funky whiteboards) so the developers can take a look at the idea and see if it's something we could work on.



As always, no promises on if and when this will make it as a feature, but I know the whole concept of multiple sites with one set of login details is high on our list of things to work on.



Thanks again for the idea :-)

Spaceman

Hi Stu,



No problem. I just seems to me that doing it this way would be the simplest (that's from a non-programmer ;-). Each individual 'Login' item could keep it's own URL, notes, title and any other info you have entered. You have just told it to go look in another 'common' location to retrieve the UserID and Password. That way, every 30 or 60 or 90 days when your work requires you to update your password for all these sites, you only have to change it once (in the 'Master' login item). I can see where it would probably have to be a manual process but that is fine with me and still is much easier than it is now.



And if that picture of you is while your in your 'office', I'll trade you my whiteboard and office any day. ;-)



Regards,



Spaceman

[Deleted User]

[quote name='Spaceman']Hi Stu,



No problem. I just seems to me that doing it this way would be the simplest (that's from a non-programmer ;-). Each individual 'Login' item could keep it's own URL, notes, title and any other info you have entered. You have just told it to go look in another 'common' location to retrieve the UserID and Password. That way, every 30 or 60 or 90 days when your work requires you to update your password for all these sites, you only have to change it once (in the 'Master' login item). I can see where it would probably have to be a manual process but that is fine with me and still is much easier than it is now.)[/QUOTE]



I think we're on the same page here, certainly a good idea, I'm no programmer either so I'm sure Dave, Roustem or Chad will find the best way to do it that has the best mix of usability and stable code.



[QUOTE]And if that picture of you is while your in your 'office', I'll trade you my whiteboard and office any day. ;-)[/QUOTE]



Sadly not, that was taken last year at my good friend Will's place in LA, had the great pleasure of staying with him and his family :-) Although having said that, the weather here in Leeds, UK today is really nice, might have to take the laptop outside for a bit :-)

dlouzan

Quick question: when you say "multiple domains", are you referring to just DNS or IP also? I manage several clustered internal machines with no DNS configuration (172.16.X.X or 10.X.X.X) and this functionality would be fantastic.

Nik

[quote name='dlouzan']Quick question: when you say "multiple domains", are you referring to just DNS or IP also? I manage several clustered internal machines with no DNS configuration (172.16.X.X or 10.X.X.X) and this functionality would be fantastic.[/QUOTE]

We're referring to the what appears in the URL field. So I could tell 1Password that amazon.com = amazon.co.uk and use the same login on both sites. I am not absolutely certain about this, but I see no reason why that wouldn't automatically extend to IP addresses as well.

WebWizard

Hi guys,



it would be great if you could add the functionality to "link" passwords to multiple sites.

For example, many sites use the Google Account to log in, so it would be great if I could link one user/pass to multiple site addresses. Then I only have to update it once in 1password when I change the password, not for every linked site.



Kind regards,

A.

[Deleted User]

Hi A,



We've had quite a few requests for this feature, where you can link multiple sites to a single username / password combination. We are looking into some options for a future update to 1Password on this, but I don't have a timeframe for exactly when this may be available.



Sorry I don't have a better answer for you right now,





[quote name='WebWizard' timestamp='1290254545' post='15529']

Hi guys,



it would be great if you could add the functionality to "link" passwords to multiple sites.

For example, many sites use the Google Account to log in, so it would be great if I could link one user/pass to multiple site addresses. Then I only have to update it once in 1password when I change the password, not for every linked site.



Kind regards,

A.

[/quote]

Granite Mac

I access 15 different URLs at work that all use my corporate Windows NT login. Because the URLs differ, 1Password treats each of these sites as if they have different usernames and passwords.



As a result, I end up with 14 duplicates of my NT password, requiring me to cut and paste my password 14 times in 1Password every time I update my NT password.



Would love ability to save multiple URLs to the same password entry.

teedoff087

Do all of the logins use the same top-level domain? If so, you could probably just change the URL in 1Password to the top-level domain.



For instance, if you had the same login for pages that use the login.google.ws domain, you could change the domain in 1Password to [b]http://login.google.ws/[/b]. The way I understand 1Password works when you fill a login is it searches for the current URL against your 1Password entries. If your domain for that particular entry only differs by page name (i.e. [i]http://login.google.ws/1.html[/i] vs. [i]http://login.google.ws/2.html[/i]), it will choose the login credentials for that particular page. Changing the domain name in 1Password to a simpler form should allow that entry to work on all pages in that domain.



It might help if you give an example of the different URLs you're working with (not the real ones, of course, but just to get an idea).



P.S. You might want to make a backup of your Agile keychain just in case this doesn't work. That way you don't have to go back and add all 14 entries.