EastcoasterWestcoaster
Level 1 (74 points)

Q: Chrome won't import Safari usernames/passwords

Sadly, I am giving up on Safari. These days every time I hit a website I suddenly get all kinds of error messages popping up about certificates being expired and authentications and yada yada yada. It's like being on someone's PC.

 

So I switched to Chrome this morning.

 

I did the Chrome>Preferences>Import data from other browser function, which showed the "import user names and passwords" from Safari as greyed out but checked.  So when I went to some typical sites that save that info for me - banking, amazon, etc. - those fields were empty. When I'd click into the username window I got a message about "would you like to allow Chrome to access your keychain" to which I say "Always Allow" - but then another message pops up saying the same thing. I say "always allow" and then -- nothing.  No info populates into my username or password fields.

 

I've googled around for a fix for this but can't find one.

 

Has anyone successfully ported over usernames and passwords from Safari into Chrome, and if so, how did you do it? I am running OS 10.6.8 on an Intel Mac.

 

Thanks,

 

Kirby

Mac Pro, Mac OS X (10.6.8), 32 GB RAM

Posted on Feb 2, 2012 11:49 AM

by Carolyn Samit,Solvedanswer
Carolyn Samit Carolyn Samit
Level 10 (124,473 points)
Apple Music
A:

Keychain preferences may be corrupted...

 

 

Quit Chrome if it's open.

 

Open Keychain Access located in /Applications/Utilities

 

From the menu bar click Keychain Access > Keychain First Aid

 

Enter your admin passwod. Click Verify. If necessary, click Repair.

 

Relaunch Chrome. Navigate to a site that requires your user name and password. You should be prompted to save that, click Yes.

 

If you still have problems, go back to Keychain Access. Select Passwords on the left.

 

Delete all keychains for sites you have problems with Chrome logging in automatically.

 

Go back to Chrome. Login to a site. You should be prompted to save your user name and password to a new keychina. Click Yes.

 

If you still have problems, go to ~/Library/Preferences/com.apple.keychainaccess.plist

 

Move the com.apple.keychain.plist file from the Preferences folder to the Trash.

 

Quit then relaunch Chrome. Try logging into a site again.

 

 

FYI.. not all sites support the autofill feature.

Posted on Feb 2, 2012 12:43 PM

Close
EastcoasterWestcoaster

Q: Chrome won't import Safari usernames/passwords

  • All replies
  • Helpful answers

  • by Carolyn Samit,Solvedanswer

    Carolyn Samit Carolyn Samit Feb 2, 2012 12:43 PM in response to EastcoasterWestcoaster
    Level 10 (124,473 points)
    Apple Music
    Feb 2, 2012 12:43 PM in response to EastcoasterWestcoaster

    Keychain preferences may be corrupted...

     

     

    Quit Chrome if it's open.

     

    Open Keychain Access located in /Applications/Utilities

     

    From the menu bar click Keychain Access > Keychain First Aid

     

    Enter your admin passwod. Click Verify. If necessary, click Repair.

     

    Relaunch Chrome. Navigate to a site that requires your user name and password. You should be prompted to save that, click Yes.

     

    If you still have problems, go back to Keychain Access. Select Passwords on the left.

     

    Delete all keychains for sites you have problems with Chrome logging in automatically.

     

    Go back to Chrome. Login to a site. You should be prompted to save your user name and password to a new keychina. Click Yes.

     

    If you still have problems, go to ~/Library/Preferences/com.apple.keychainaccess.plist

     

    Move the com.apple.keychain.plist file from the Preferences folder to the Trash.

     

    Quit then relaunch Chrome. Try logging into a site again.

     

     

    FYI.. not all sites support the autofill feature.

  • by EastcoasterWestcoaster,

    EastcoasterWestcoaster EastcoasterWestcoaster Feb 2, 2012 12:45 PM in response to Carolyn Samit
    Level 1 (74 points)
    Feb 2, 2012 12:45 PM in response to Carolyn Samit

    Thanks Carolyn.  I did this, but going to a website like Chase.com after this process still presented me with an empty username field.  I suppose I could just reenter usernames and passwords for every website that I use, but that's just too much work. Definitely an exercise in frustration!  So at this point I think I'm going to dump Chrome and just move back to (buggy) Safari.  Dealing with its foibles is actually less frustrating than having to remember & re-enter all those usernames/pw's on all those websites!

     

    Thanks for the help, much appreciated... and marked "Solved."

     

    Kirby

  • by Carolyn Samit,

    Carolyn Samit Carolyn Samit Feb 2, 2012 1:03 PM in response to EastcoasterWestcoaster
    Level 10 (124,473 points)
    Apple Music
    Feb 2, 2012 1:03 PM in response to EastcoasterWestcoaster

    When you sign in to your Chase account you should see this...

     

    Chase ASC image.jpg

     

    Make sure you select:  Remember my User ID

     

    Keychain Access stores your passwords, not user names. Some sites allow to store the user name for you, some don't. Chase should save your user name if you select the: Remember my User ID box. Quit the browser, relaunch the browser, try Chase.

     

     

     

    about certificates being expired and authentications

     

    Make sure the Time & Data are correct on your Mac. System Preferences > Date & Time

     

     

    edited by:  cs

  • by EastcoasterWestcoaster,

    EastcoasterWestcoaster EastcoasterWestcoaster Feb 2, 2012 1:03 PM in response to Carolyn Samit
    Level 1 (74 points)
    Feb 2, 2012 1:03 PM in response to Carolyn Samit

    Oh I understand what I'm supposed to see and I know about ticking the "remember user ID" box.  My problem is that if I switch to Chrome, I then have to re-enter my username and password for every single website I use that requires a username and password because Chrome can't see my Keychain and can't import my passwords and usernames from Safari. That's several years' worth of websites that I use routinely, whose usernames and passwords are all different because of the unique requirements of each website.  So rather than go through that exercise in frustration, I'm just going to stick with Safari and hope that the kinks get ironed out.

     

    Kirby