Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

When I navigate to my work's Outlook Web Access site to read my emails, Google Chrome 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 that,

  1. If I click CANCEL on the first dialog it takes me to the OWA screen and I can log in normally anyway. However - subsequent 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).

share|improve this question

If your organization is using a logo or retrieves any of the images using an FTP path, you'll have to authenticate for that FTP connection. This would be why, even if you don't authenticate, you can still get to the OWA site. Have your OWA admin check where the images are being hosted from and redress (move them to your company website perhaps?) accordingly.

share|improve this answer

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.

share|improve this answer

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.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .