-
Notifications
You must be signed in to change notification settings - Fork 6
Third party configuration for Kerberos
Francois Levaux-Tiffreau edited this page Oct 29, 2015
·
1 revision
By default, Google Chrome doesn't trust Kerberos. Activate it this way:
$ defaults write com.google.Chrome AuthServerWhitelist "*.example.com"
$ defaults write com.google.Chrome AuthNegotiateDelegateWhitelist "*.example.com"
You an also push this as a profile:
<plist version="1.0">
<dict>
<key>PayloadContent</key>
<array>
<dict>
<key>PayloadDisplayName</key>
<string>Google Chrome Kerberos</string>
<key>PayloadEnabled</key>
<true />
<key>PayloadIdentifier</key>
<string>com.google.Chrome</string>
<key>PayloadType</key>
<string>com.google.Chrome</string>
<key>PayloadUUID</key>
<string>61337621-A524-4C8C-BF90-7D9EB6C9C314</string>
<key>PayloadVersion</key>
<integer>1</integer>
<key>AuthNegotiateDelegateWhitelist</key>
<string>*.example.com</string>
<key>AuthServerWhitelist</key>
<string>*.example.com</string>
</dict>
</array>
<key>PayloadDescription</key>
<string></string>
<key>PayloadDisplayName</key>
<string>Google Chrome Kerberos</string>
<key>PayloadIdentifier</key>
<string>61337621-A524-4C8C-BF90-7D9EB6C9C314</string>
<key>PayloadOrganization</key>
<string></string>
<key>PayloadRemovalDisallowed</key>
<false />
<key>PayloadType</key>
<string>Configuration</string>
<key>PayloadUUID</key>
<string>61337621-A524-4C8C-BF90-7D9EB6C9C314</string>
<key>PayloadVersion</key>
<integer>1</integer>
<key>PayloadScope</key>
<string>User</string>
</dict>
</plist>
Remember to change UUID with $ uuidgen