I've seen a couple of discussions on JAMF Nation about kerberizing Chrome using command-line switches, MCX, and Chrome's "preference list" and I was hoping someone could help me figure out an issue I'm having or at least verify that I'm not the only one having the problem.
I'm trying to use WGM/MCX (locally while testing) to enable kerberos using the "AuthServerWhitelist" parameter. I can see that the policy policy is being applied to chrome when I type chrome://policy into the browser; however, when I try to go to an internal site I'm prompted for my user ID and password (NTLM Auth).
If I launch chrome using the following string from the command line and try to access the same site I'm not prompted for my credentials and kerberos works as expected:
open -n -a 'Google Chrome.app' --args --auth-server-whitelist="site1,site2,site3"
In order to make sure that MCX policies were working I added another parameter to the policy "AuthSchemes" and enabled "Negotiate,Digest" (leaving NTLM out on purpose).
After refreshing the policy and trying the same site again, I was immediately denied access, since Chrome was forced to not default to NTLM - this tells me that Chrome is reading and enforcing policies fed to it by local MCX.
So I'm left scratching my head wondering why it will not honor or enforce the "AuthServerWhitelist" policy.
Has anyone else experienced this or know how to fix it besides feeding Chrome the white list from the command line at launch?
