Is there a better way? add new Login/Item to 1Password database from browser page

helppls

Hi: I know many times the item I wish to add is NOT in my 1Password database. I do not need to search and check, so I am getting tired of the amount of clicks to get to the spot to save the new login. So I wondered is there a better way?

Often I start at a "Registration Page" v. "Login Page". If I want to add a new Login from registration this is what happens for me:
3 movements on trackpad
1. First Click to open the Fx addon
2. then move over to right hand side cog (its quite a distance for me)
3. then Second Click on Cog to trigger add new login

And then when registration confirmed
The browser URL stored in 1password will be incorrect as the registration page is not the same as login page. So when I first login, I need to update existing login. Not always this option pops up. Maybe only 20% it does not. For this 20% I then open 1password on desktop and manually paste the URL as a second URL option. Hoping (not yet fully trusting) it will work 3rd time.

Conclusion: I feel there must be an easier way. My brain is thinking of options....
maybe

• double tap on the Fx icon addon to go immediately into add new login mode, and single tap on Fx icon to go into popup.
• or maybe, single tap to go into add new item mode, hover to get lookup (like in LittleSnitch Monitor preferences you can set the time you want the lookup box to stay open on hover then auto-close), and double tap to get search mode

Perhaps these settings are better set as preferences.

But as it stands now, for me it has the OLD menu structure mentality that works well on mouse but gets tiresome on trackpad/touch.

Another Alternative: I could stop registering on the sites I visit and go back to being anon.

littlebobbytables

Hi @helppls,

What we'd recommend is only saving the Login item from the login page rather than the registration page. When we save a Login item from the extension we inspect the page and record all the fields used. The registration page will likely hold a lot of unnecessary information and there is a reasonable chance the fields won't match up with the login page in a meaningful way - imagine the Login item as a snapshot of the login page.

What I tend to do is after I've registered on a new site I'll immediately log out (if they logged me in as part of the process) and save a proper Login item. As I use unique email addresses at each location that means a little more faffing around for me as I need to temporarily record both a password and the email address for the period between registering and creating the Login item. Now given I'm not registering with sites on a massively frequent basis, even including the website troubleshooting I might do here in the forums, I don't find this particularly onerous at all but tastes do vary.

This will hopefully allow you to save once rather than suffer a lot of adjusting after the initial save. If you use 1Password's Password Generator then it might be useful to know that when you copy or fill the generated password, a Password item is created so you have a copy of it. If you later then create a Login item for that same domain using that password the Password item will be removed. Until that happens though you should always find a copy of any used password in the Password item category.

Does this help at all?

helppls

Thankyou littlebobbytales for trying to help. Your method will not work for me.

I am so hopeless by the time I login, after registering, I kept forgetting the information. I know it sounds absolutely silly but really I do. Sometimes it takes a while before my forum access is activated. So I cannot login immediately. So I started writing them back in my text file. Then I said after a few months. No, this is crazy, 1password I promised myself I would only record the passwords in there.

Thus for me, I need to create the 1password login entry at time of registering not first time login**.

Secondly, I have 5 email addresses, as I use these for specific things. So then on my iphone I only receive certain email content. I know I could filter, but its simpler for me to do it by email addresses versus email content. So I need to record the email address I used.

Thirdly, you are correct, the fields often do not match up. Then I have to edit them.

So its actually not very suitable for forum and community registrations/logins. Its create for website logins where I get immediate access.

littlebobbytables

Hi @helppls,

Sadly I don't think there is a technical solution, at least not one that I can think of at the moment.

The crux of it is the registration page is invariably different from the login page and this is outside our control. It would also seem likely that they will remain different because of their different purposes.

For sites where the account is activated instantly upon registration my suggestion should still hold. It does mean a couple more steps at the time but I personally like knowing there and then that I have a working Login item so I don't need to think about it later.

For sites where there is a significant delay between registration and account activation all I can suggest is either continuing with your current workflow or consider creating what I refer to as basic Login items. A basic Login item is where you create a new Login item from within the main 1Password window. This Login is completely bare and will only have the details you add. So you would manually enter your selected username and password, add the URL and if need be you can add a custom field for your email address. The custom field is what I do given I create unique addresses for each site. Now there is no guarantee a basic Login item will work but they often will without any further amendments.

That's the current state of play. So for the moment it would be about finding what works the best for you given knowledge of these options. If we can assist with anything else please do let us know.

helppls

I used the drag of the URL (had registration page and the login) today. Login came in about 4hrs later.
So my workflow I tweaked based on your replies
1. I made sure I was at login page (url)
2. I opened up the entry in 1Password Mini, cut and pasted the login from the saved entry that I made during registration
3. Then clicked edit (dont like where the edit icon is by the way)
4. cut and pasted the URL from the URL login page into add another URL
5. dragged the URL login page up to position 1 (thankyou for this tip!)
and saved.

Then logged in.

Ideally 1Password Mini, would have an option to check URL on domain level I guess... ( but here I was thinking that cannot be too technical as after all the domain is the same) so then it would do all the above automatically for me.

littlebobbytables

Hi @helppls,

The only concern I have is that I strongly suspect that workflow won't work for a large number of sites. Just off the top of my head I can visualise three groups at the moment

• The first group are those sites that use a nice, clean page for registering and another for logging in. They've kept it clean and simple and your approach works.
• The next group are those sites that still have separate pages for registering and logging in but for whatever reason, form ID reuse possibly or other gotchas, the only solution is to create a new Login item from the extension so it properly records the details required.
• The last group are those sites that actually have both the registration and login forms on the same page. Creating the Login item during the registration process would always mean those fields being filled in on repeat visits. Again, your only option would be to create a brand new Login item with the login fields filled in.

Those are just the ones that spring to mind and if I've learnt anything during my time here at AgileBits it is web developers are inventive, very inventive.

Your idea could work for a certain set of sites but unfortunately I believe it would break down for many others. At the very least though it will work for some and as long as you're aware of why it may not work all the time you won't be caught completely off-guard :smile:

I do understand the appeal of reducing the number of steps involved in creating a new Login item, I'm just not sure there is enough standardisation (or will ever be) in how somebody can build an interface that both registers and logs a person in for us to be a lot more intelligent about it. Better minds may disagree though :wink:

helppls

Yes, your perspective is valid.

If we only have 3 use-cases, that would be amazing...
Handling these 3 common use-cases is not a big ask.

The alternative is I go back to what I was doing pre-2015, only record website app logins, not website forum logins. Go anon on website forums + website blogs. I was trying to be less anon as there is benefit to the provider of the forum and blog was my thinking.

littlebobbytables

Hi @helppls,

While I used a categorisation that allowed me to split sites into three groups, groups 2 & 3 would both mean 1Password having prior knowledge of every site that this applies to. We'd have to manually encode this kind of information into the application and we would need to keep it up to date too as sites change. Basically it would require a mapping where we recognise saving of a particular registration page and we check the field details for said page. We then map the contents of certain fields to the previously discovered fields of their login page and this would all be per site. The reason this would be per site is HTML allows an impressive number of ways of describing even a simple page and many pages are far from simple.

The question that would have to be asked is, would enough people benefit from such a feature given the ongoing requirements it would have. It may be this is something that could be semi-automated, where a site is flagged for manual checking when an automated check finds it differs from the historical record. The designers would have to investigate the feasibility though. As I say, I suspect any feature like this would have to be manually monitored and as such, its usefulness monitored.