Exact URL Rules

JoshFinks

Hopefully someone can help me out here as I'm sure I'm missing something easy.

Just so you know, I'm coming from Lastpass. I'm actually trying to get this set up for my mom. I'm trying to find something easy but that will allow her to work without it being convoluted.

Let's say that I have a bunch of wordpress sites and they all have their own login. In LP I could set up a URL rule that would say that for Wordpress.com domain each subdomain would have it's own LP site and it would know which login went where.

In 1P I don't see this. If I have 2 different wordpress sites. i.e. sitea.wordpress.com and siteb.wordpress.com it seems that it doesn't autofill but I have to drop down the list and select which password I'm looking for.

Am I missing something or is this just how it works?

Thanks

Josh

Jasper

@JoshFinks That's just how it works.

I think lots of others would like to see this addressed as well.

Here's just one existing topic about it: http://discussions.agilebits.com/discussion/comment/83679/

JoshFinks

This is disappointing. Between this and the inability to fill Basic Auth forms in browsers I'm not sure why I would use this. I'm kind of disappointed I paid for the upgrade.

bittwister

This worked fine in version 3. I've opened a support case to see if they can do something about it.

MikeT

Hi guys,

The ability for 1Password to fill in directly based on the subdomain listed in the Login is currently not so good with its accuracy, it worked on some sites but not as good as it was in 1Password 3. We're aware of this and are working on improvements.

If you can give us the sites where it didn't work properly, we'll add it to our issue on this. We'll test it once we make the improvement to ensure it's working better.

inability to fill Basic Auth forms in browsers

There's nothing we can do about Basic Auth, those dialogs are not from the sites itself but rather separate dialogs that comes down from the browsers themselves. These are areas that extensions cannot hook into, extensions can only modify the toolbars and the website, nothing else.

All of our extensions complies with the browser's APIs to ensure that they don't break us whenever they update/upgrade. Unfortunately, right now, the APIs don't offer anything for Basic Auth or if there are some, it doesn't work the way we want it to. LastPass, according to customers here, does this with binary workarounds, which is something we won't do without breaking the compatibility with the future browser versions.

JoshFinks

Here is a place where exact URL matching is needed :

For my gap credit card they have multiple screens (so does Bank of America)

The first login page asks for your username :
https://www3.onlinecreditcenter6.com/consumergen2/login.do?subActionId=1000&clientId=gap&langId=en&accountType=plcc

Once it has verified the username it then asks for a password on the next screen : https://www3.onlinecreditcenter6.com/consumergen2/consumerlogin.do

I can manually save these but then when I get to the page I have to go to the 1P Mini and select the Username field (which even though it's checked it does not autosubmit). Then I click login and then the password screen is the same thing, go to mini, select it and then click submit.

IMO this should be at the very least something that fills in the fields even if I have to hit login or submit manually.

Thanks

MikeT

Hi @JoshFinks,

Those are the same site addresses. If the subdomains were different, 1Password could detect which Login item belongs to a specific subdomain. It doesn't do subpath matching, only subdomains.

What you could try is open the main 1Password app, create a new Login item, enter your username/password, and set the URL to https://www3.onlinecreditcenter6.com/consumergen2.

After that, try selecting the same newer item on both pages, see if 1Password can fill both.

JoshFinks

I guess when I talked about "Exact URL Urls" I didn't explain it properly. The way it has worked with LP was that it looks at the exact URL you are using, whether it's a subdomain or a different URL. Otherwise how specifically do you account for websites that use one page for logins and one page for passwords and then one page for other questions as well?

Maybe I just have a different workflow than most people?

sjk

Hi, @JoshFinks.

The current method for handling sites with multiple pages of authentication credentials is to create a separate login item for each page, as described in:

Create multi-page logins

If that's what you're already doing is it just the auto-submit part that's not working?

As @MikeT mentioned, we're working on improving accuracy for subdomain-based filling. And support for URL matching beyond the domain and subdomain level is something we're still evaluating.