Sorry for the delay—just wanted to provide some clarity around the issue above with macOS Platform SSO and Google Chrome.
Several users were being prompted to reauthenticate multiple times per day (sometimes every time they accessed an SSO app). After some digging, I found the issue was related to how our Google Chrome extensions were being deployed via Configuration Profiles.
Specifically, we had multiple Configuration Profiles applying settings to the same preference domain (com.google.Chrome), each defining different extensions using the Application & Custom Settings payload. This caused inconsistent behavior—Chrome wasn’t reliably enforcing or displaying the extensions, which led to the SSO instability.
The fix that worked for me was to consolidate all extension settings into a single PLIST and apply it via one Configuration Profile. Splitting them across multiple profiles created conflicts or race conditions during enforcement.
I’ve attached:
-
A screenshot of the merged config
-
An older config profile labeled "OLD" for reference
Hope this helps someone avoid the same headache!
