Yosemite and Chrome (64bit) misbehavior in 1P 5 for iMAC

SSALTWICK
SSALTWICK
Community Member

I am a new user - so this could be operator error - I hope so. But I am having a terrible time getting 1P to work on my new iMAC.

I am running OSX 10.10.1 on a 5k retina iMac. SSD and 16G memory
I have CHROME Version 39.0.2171.95 (64-bit)

I just have a few logins installed - I am trying to get the hang of it.

Now - some simple logins work. i.e. single page signons - user name and password on same page - very simple web pages.

BUT

Citibank and Fidelity so NOT work.

I am using simple passwords so that I can manually key them in if necessary. I have multiple tabs open in Chrome and I have enabled the proxy bypass (as discussed in a previous discussion note).

For both of these web sites - I load the login page into a new Chrome tab. I position the cursor to the user name filed, then hit the 1P button on Chrome. I then click on the login for that site. The login fails with an error like "username and/or password is not correct" I can see the user name and it is fine. I can also manually enter the password (the same as entered in 1P vault) and the login SUCCEEDS.

Tried this many times. I do not think it is all me - since I can get a least one simple logon to work.

Help - this seems like very simple stuff - 1P should be able to do this. So, what am I doing wrong?

Comments

  • Stephen_C
    Stephen_C
    Community Member

    There have been several threads about problems with Citibank sites, including this one. You might have a look at that and see if there's anything in that which helps you. A forum search on "Citibank" (without the quotation marks) discloses a number of other recent threads which may help.

    There's also a recent thread about problems with Fidelity, with this comment from AgileBits about a known problem with the site.

    Sorry not to be more constructive.

    Stephen

  • SSALTWICK
    SSALTWICK
    Community Member

    Stephen_C
    THANK YOU!

    The problem was both sites masked the user name with ****** and that is what I was saving in the logon!

    I followed the suggestion of the manual workaround you pointed me to -- i.e. go BACK and put the cursor in the USERNAME field BEFORE you save the logon - and THAT WORKED!

    You can also tell if you have a problem by looking in the mini-app. If you see a user name with **** in the username field - then you have a problem. I deleted those fields, added the new logon (with the ****) and then all worked.

    Both sites are now working as expected!

    Cheers
    Steve

  • littlebobbytables
    littlebobbytables
    1Password Alumni

    Hi @SSALTWICK‌ I'm glad to hear @Stephen_C managed to help you out. Some sites actively do their best to stop the likes of password managers from working in the belief that forcing people to type stuff in is more secure. Personally I don't agree given it means you need to simplify the password so it's more memorable and less prone to typos.

    As your issue is resolved I'm going to go ahead and close this thread but if you have any further questions or issues do please ask and we'll see if a member of AgileBits can beat Stephen_C to the thread :stuck_out_tongue:

This discussion has been closed.