New tab that will get me to that site does not open when I click on a login item

daniels

Hi,

I have the following issue: I have multiple sites on various subdomains of the same domain (site1.something.net, site2.something.net) and I have saved different logins for each of them.
If I go and click on a login item a new tab will open in Chrome and will get me to that site (site1.something.net) and autocomplete the username and password (which is perfect).
The problem is that if I keep this tab that I was just directed to active and I go back to 1Password and click on a different login item (that is for a different website on different subdomain of the same domain that the current tab is - site2.something.net) nothing happens.
If I switch to a different tab (that has a page from different domain loaded), or open a new empty tab and then I go and click again on this second login item (site2.something.net) now it works and I am redirected to this site and have my username and password autocompleted.

---

1Password Version: 5.3.2
Extension Version: 4.4.1.90
OS Version: OS X 10.10.4
Sync Type: Folder in iCloud drive

JWeaver

Hi,

The first thing I would recommend checking is Lenient URL matching.

daniels

Lenient URL matching is unchecked.

littlebobbytables

H @daniels,

I don't have many options when it comes to testing subdomains but I did test one of the few I know of. For me everything seemed to work as be both believe it should, with focus on a tab loaded with one subdomain, using open and fill from the main 1Password window opened a new tab, loaded the URL for the other subdomain and proceeded to fill.

Normally I ask which version of Chrome somebody is running as we do see a certain variability if somebody is running a beta or other but it turns out I was still running the dev build for my first test. Switching to the stable resulted in the same expected behaviour so it doesn't seem to be that this time.

All I can think to suggest right now is to try a reboot and see if the behaviour is reproducible afterwards and to ask if you make use of multiple profiles (or people as Chrome calls it).

Certainly an odd one and we'll do what we can to get to the bottom of it.

daniels

I use Chrome 43.0.2357.132 (64-bit) (so usual stable version).
I did tried to reboot, I actually shutdown the Mac each night and I noticed this issue since I've installed 1password the first time but I've only reported it now.
I could give you a video recording of the screen of me doing this and reproducing the issue but I can't post it in public due to some NDA issues.

daniels

I've just discovered something. Looks like this issue is happening only when I have the Chrome extension enabled. If I go to chrome://extensions/ and I uncheck "enabled" for "1Password: Password Manager and Secure Wallet 4.4.1.90" then everything works ok and my new tabs are opened corectly. When I enable the extension back the issue that I described above is happening again.
So I guess the issue is with the extension.

BTW do I really need the extension? What exactly does it do? As from what I've noticed everything seemed to work without it also. I've only installed as it kept bugging me to install it each time I was clicking the "1password" icon and haven't found a way to disable that prompt and let me use 1pass without the extension.

littlebobbytables

Hi @daniels,

Thank you for the offer of a desktop video capture. If it turns out to be useful in understanding why then we may ask you and of course we will do so via a slightly more private medium other than the forums :smile: At the moment though it isn't the case that I don't believe you, it's trying to figure out why are two systems are behaving differently.

The extension is required, at least if you want proper filling to happen. The role of the extension these days is to view the DOM of the page you wish to interact with and report back to 1Password mini. 1Password mini decides how to approach this page and then passes all of the details back to the extension so the extension can alter the page which we view as filling. Without the extension we cannot fill.

So it does pose a question. It sounds like you're saying filling happens even if you disable our extension and that doesn't sound right. The easiest way forward may be for us to review a diagnostic report. This guide will assist in creating one.

• For 1Password on your Mac

Please do not post your Diagnostics Report in the forums

The email address you will want to use is support+forum@agilebits.com.

When sending the diagnostic report to the address above it would help immensely if you could include a link to this thread and your forum handle so we can connect the two.

Once you've sent the report a post here with the ticket ID will help us to keep an eye out for it. With access to the report we should be able to better assist you :smile:

daniels

My bad. Filling does not happen with the extension disabled. Only new tab is opened. The problem with subdomains is still present and I've sent an email to support+forum@agilebits.com

Ticket ID PQG-83919-833

Drew_AG

Hi @daniels,

Thanks for sending the Diagnostics Report! I'll update the email thread with details from this forum discussion so it's easier for our support team to get up to speed with the issue. Someone will get back to you as soon as possible with more information, and we'll keep the conversation going directly via email to avoid complicating things between here and there.

ref: PQG-83919-833
ref: OPX-1028

daniels

FYI: This issues seems to be on multiple domains. (and not just the one I've send in the email).

For example I'm on a tab in Chrome that's on https://dev.domain.com/path/to.stuff and if I click on a login item for http://jenkins.domain.com/ I don't get a new tab opened and nothing happens.

If I manually open a new tab and switch the focus on that then it works. So looks like there's a bug with LOGIN item to URL matching.

Drew_AG

Thanks for taking the time to let us know! Indeed, this issue seems to happen with various sites. I apologize for the inconvenience! In case it helps our developers, I'll add your new comments to the bug report.

ref: OPX-1028

daniels

No problem.

By the way, in my opinion I think the matching should be done based on what we enter in the website field.
So for example if for a login I enter "http://www.domain.tld/path/" then you should match this login to "http://www.domain.tld/path/" and below (eg: "http://www.domain.tld/path/(.*)")

Not sure if it's the "right" way but it should be more flexible than it is now.
(just trying to provide some feedback)

Anyway my trial expires in a few days and I'll get the full version so I hope this can be fixed in a future update.

littlebobbytables

Hi @daniels,

So we've got the bug which obviously we need to get fixed. I hadn't stumbled upon that one yet which surprises me a little given we do have a couple of subdomains here that we use.

Now for the flexibility, we use the full path for the likes of open and fill but we will match against the domain for the purposes of displaying in 1Password mini. The way it works is we favour the full domain (I'm sure there's a correct term to be used which I don't know) but the raw domain + subdomain. All of those are the 'exact' matches. Then we will also list anything that doesn't match on the subdomain but does on the raw domain. If you have lenient URL matching on they're all listed in one go, otherwise they're always hidden unless we want to talk about the edge case of just two items matching.

So under normal behaviour, without silly bugs getting in the way, I think the extension should be behaving in a way that works for you. Please do let us know if I've misunderstood something though.

daniels

Hi,

Yes, I think that will be ok (if I also understood correctly :) ) so I'll wait for the update and see.

littlebobbytables

:+1: :smile: