Latest Google Chrome 101.0.4951.41 break anything?

[obi-k]

Did the latest Chrome (101.0.4951.41) break anything in your environment?

In particular, SSO/SAML?

[geoff_widdowson]

Tested SSO and no issues for me, so far.

[pete_c]

No SSO issues with Chrome v101 so far, deployed to production 36 hours ago.

[applebravo · Accepted solution]

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

[Asifahmed]

These two new commands are NOT working for me. Google Chrome 102 version , any idea?

[eargueta]

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>

[Asifahmed]

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?

[obi-k]

@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.

[Asifahmed]

Can you please guide me to do it, I need some help here. I have Google Chrome version 102

[eargueta]

This was a good finding, I was able to make the change and it worked like Charm. I appreciate you posting this.