1Password on Mastodon

Autofill inconsistencies

Hi I use 1Password for work and have the following issue.

When i first try to use the browser plugin to populate my credentials it doesn't select the right one by default (or recognize that there is another match) until i open 1Password and re-edit the login entry

I have 2 1Password entries (with different username + password entries)
Staging Site:

Forefront Security:

Steps to re-produce
1. I try to access the clients staging site http://staging.myclient.com/sitecore
2. I am redirected to http://staging.myclient.com/CookieAuth.dll?GetLogon?curl=Z2Fsitecore&reason=0&formdir=3
3. I press [ctrl] [] - the form is filled with the Staging Site credentials (which don't work)
4. I open 1Password + Edit the Forefront Security entry
5. I go back to the browser and press [ctrl] [] again - the form is filled with the correct account details

Why might this be an issue?

OS: Windows 8.1
Firefox 37.0.1
1Password: 4.3.1.560

Comments

  • littlebobbytableslittlebobbytables
    1Password Alumni

    Hi @MarkWiseman,

    I'm not a massive Windows user but I launched a VM I have and went to work seeing if I could understand what was going on. I don't know if what I've found is relevant or not but let's see :smile:

    I have a test vault and in it I had two items for Facebook and their URLs differed by a single character:

    1. https://www.facebook.com
    2. https://www.facebook.com/

    Yup, the difference was a trailing forward slash. That was enough for to automatically fill one and not offer the option. This is also true in the beta.

    So I suspect it's down to a bug in 1Password for Windows. I'm guessing the URLs stored in your items are different^ which combined with this bug might explain what you're seeing. I'm going to ask one of the team more familiar with Windows to chime in here (@MikeT). The extension itself is platform independent so the fact that I've always been offered a choice between those Login items suggests to me it's something specific to Windows. Let's see if @MikeT can shed any light.

    ^ I wasn't sure if the URLs you supplied were to just to explain the URLs involved or if they were the exact URLs stored in the items too. What I also wasn't sure about was if the staging site URL redirects you why do you have a Login item for it? There's undoubtedly a good answer I'm sure :smile:

  • MarkWisemanMarkWiseman
    Community Member

    Hi @littlebobbytables thansk for you help.
    Apart from the domain name i used in the example those are literally the URLs that I use.

    The only difference is that the actual Forefront URL appends a few query string values
    CookieAuth.dll?GetLogon?curl=Z2F&reason=0&formdir=3

  • littlebobbytableslittlebobbytables
    1Password Alumni

    Hi @MarkWiseman,

    As an experiment, if you were to alter the URLs so that they all used just the domain .e.g http://staging.myclient.com does 1Password behave in a more consistent way? Obviously this isn't a solution as open and fill wouldn't work any more but I just wondered if it would suggest my findings are related or not.

    Hopefully @MikeT can weigh in here :smile:

  • littlecharvalittlecharva
    Community Member

    Hi @littlebobbytables,

    You pointed me to this thread from my similar question. Changing the URL for all of my accounts to just the domain as you've suggested above DOES make the Windows 1Password Chrome extension behave as expected.

    Anthony

  • MarkWisemanMarkWiseman
    Community Member

    @littlebobbytables I had tried this before, I was just hoping the URL matching was smart enough so I didn't have to make a selection. They are stored as 2 different URLs.

    Its just a kink in 1Password's shining armor.
    It works... But it could work better

  • MeganMegan
    1Password Alumni

    Hi Anthony ( @littlecharva ),

    I'm so glad to hear that this suggestion got you straightened out! Thanks for letting us know. :)

    Hi @MarkWiseman,

    I'll let our development team know about this so we can see if there's anything to be done to polish up 1Password's armour here.

This discussion has been closed.