Google Chrome not offering to save passwords

09
2013-08
  • JD Isaacks

    My co-worker is using Google Chrome but cannot get it to offer to save his passwords.

    He is on XP with Chrome version 6.0.472.63

    I made sure that "offer to save passwords" is selected in options and cleared all his browsing data. It still won't offer.

    I am using the same version of Chrome on Win7 and it saves my passwords for the same sites.

    I am not sure what else to try?

    • Answers
  • blackmastiff

    In my experience, Chrome will never offer to save passwords for protected directories, nor will any of the password managers that I have used. AFAIK, I don't think that it's possible at this point. Sorry I couldn't help more.

  • sonoftsadik

    He may have disabled sites in the past. If you click "Show Saved Passwords" from the options and then click the "Exceptions" tab, you can reset the settings per site. Next time he visits the site it will ask again.

    Hope that helps!


    • Related Question

    browser - Google chrome asking for username and password for OWA
  • Grant

    i have a question about the google chrome browser.

    When i navigate to my work's Outlook Web Access site to read my emails, the chrome browser is prompting me for a username and password to the server saying "Authentication Required - the server XXXXXX.XXX:443 requires a username and password.

    After i put them in i then have to enter in the normal OWA username and password to access my emails as per normal.

    The funny thing is..

    1] If i click CANCEL on the first dialog it takes me to the OWA screen and i can log in normal anyway. However - subqeuent page clicks will keep prompting me each time for the server credentials.

    2] I am NOT prompted for server UN and PW if i use IE or fireFox.

    Does anyone know how to stop chrome from asking me each time? or is it a server setting - i do know that a friend who uses the same browser (chrome) and also OWA does not have the same problem (NB: they work at a different company)

    Thanks!


    • Related Answers
  • dlamblin

    This is probably a proxy username and password having do do with either a pac file that chrome doesn't auto-discover, but IE and Firefox do or NTLM authentication. And yes, some proxies will ask for authentication, then proceed to function just dandy without being authenticated, although they will keep asking.

  • Anthony

    Try putting in the full path to the OWA site in Chrome, including the "https://", I've noticed on our WES that if you don't put the https:// and if you leave off the /owa at the end, it will flash an error page that redirects to the main login. So maybe Chrome handles that redirect page differently.