Did the latest Chrome (101.0.4951.41) break anything in your environment?
In particular, SSO/SAML?
Solved
Latest Google Chrome 101.0.4951.41 break anything?
+20Best answer by applebravo
Yes google changed some wording for the latest version of chrome so we had to update our scripts.
New commands:
defaults write com.google.Chrome AuthServerAllowlist "https://example.com"
defaults write com.google.Chrome AuthNegotiateDelegateAllowlist "https://example.com"
Old commands: was using AuthServerWhitelist and AuthNegotiateDelegateWhitelist
+8Tested SSO and no issues for me, so far.
+16No SSO issues with Chrome v101 so far, deployed to production 36 hours ago.
+8Yes google changed some wording for the latest version of chrome so we had to update our scripts.
New commands:
defaults write com.google.Chrome AuthServerAllowlist "https://example.com"
defaults write com.google.Chrome AuthNegotiateDelegateAllowlist "https://example.com"
Old commands: was using AuthServerWhitelist and AuthNegotiateDelegateWhitelist
+20@applebravo Looks good so far! How did you find this out?
I updated the preference domain file with those new commands and it's working again.
+7This was a good finding, I was able to make the change and it worked like Charm. I appreciate you posting this.
+9Yes google changed some wording for the latest version of chrome so we had to update our scripts.
New commands:
defaults write com.google.Chrome AuthServerAllowlist "https://example.com"
defaults write com.google.Chrome AuthNegotiateDelegateAllowlist "https://example.com"
Old commands: was using AuthServerWhitelist and AuthNegotiateDelegateWhitelist
These two new commands are NOT working for me. Google Chrome 102 version , any idea?
+9@applebravo Looks good so far! How did you find this out?
I updated the preference domain file with those new commands and it's working again.
Can you please guide me to do it, I need some help here. I have Google Chrome version 102
+7These two new commands are NOT working for me. Google Chrome 102 version , any idea?
I created a configuration version for com.google.Chrome to be push with clients that got upgraded with the edit strings I had to do within it. Because the old command had Whitelist vs new (Allowlist). Any version for 101.0.4951.41 or after will need this to be modified and pushed.
<key>AuthNegotiateDelegateAllowlist</key>
<string>*.xxxx.xxx.com,*.xxxx.xxx.com</string>
<key>AuthServerAllowlist</key>
<string>.xxxx.xxx.com,*.xxxx.xxx.com</string>
</dict>
</plist>
+9I created a configuration version for com.google.Chrome to be push with clients that got upgraded with the edit strings I had to do within it. Because the old command had Whitelist vs new (Allowlist). Any version for 101.0.4951.41 or after will need this to be modified and pushed.
<key>AuthNegotiateDelegateAllowlist</key>
<string>*.xxxx.xxx.com,*.xxxx.xxx.com</string>
<key>AuthServerAllowlist</key>
<string>.xxxx.xxx.com,*.xxxx.xxx.com</string>
</dict>
</plist>
It worked now, just curious to know that, why it is not working if I run the command mentioned by B_Shades? And How to know that Google changed this command?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.