Enabling Integrated Windows Authentication in Chrome on a Mac

Google Chrome logo

I was surprised at how difficult it was to find this information, given that Chrome is certainly one of the most widely-used browsers in the world, and also that it is commonplace to have Macs connecting to Windows domains.

I found that the domains that would be sent IWA information are set in the AuthServerWhitelist policy. But how to change these policies?

After coming across this article, it appeared that changing the policy via the Terminal window would be the best – and possibly only – way to do this.

Enter the following line into Terminal, using comma-separated domains that you trust with your credentials (with or without wildcards), and press Enter.

$ defaults write com.google.Chrome AuthServerWhitelist "*.domain1.com, *.domain2.net, *.domain3.org"

Restart Chrome.

By accessing chrome://policy, now, you can see the new domains in the policy setting.

Chrome Policies page

While this has not proven to be foolproof – some domains still prompt for a user name and password – it seems to work more often than not.

Chrome Developer Tools Not Working

Developer Tools is disabled

Recently I had to replace my Windows PC at work, and as a result, had to reinstall all of my applications, including Google Chrome. When I tried to open Chrome Developer Tools using the F12 key, nothing happened. The Inspect option seen when right-clicking on a web page was grayed out. I opened the drop-down menu to try to open DevTools from there, and that option was also grayed out.

Developer Tools is disabled

Several searches indicated that one could look at Chrome Policies (accessible at chrome://policy if you’re running Chrome) to see if it was disabled there. Sure enough, that was the case.

Chrome policy page showing DevTools disabled

Chrome Policies are not editable from this page; in Windows one must edit them via the Windows Registry.

Open the Registry using regedit.exe from a Command Prompt or a shortcut in the Start Menu, and navigate to [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome] and set the key called DeveloperToolsDisabled to 0.

Registry Editor showing [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome] branch

Close the Registry Editor, go back to the Chrome Policies tab, and click the Reload button in the upper left-hand portion of the screen.

The “true” value for the DeveloperToolsDisabled Policy Name should change to “false”.

Now you should be able to open DevTools again!