Skip to main content

Have recently built out a PlatformSSO config, and have seen varied results upon the devices on which I’m testing it. To my understanding it appears one has to scope a minimal AppSSOKerberos config in order for the PSSO config to properly register. I say this because, and this only appears to effect Apple Silicon devices running macOS 15+, when the config appear to bork itself registration is always unsuccessful.

The underlying cause seems to be simultaneous writes to the AppSSOAgent and the AppSSO Daemon; what then happens is that underlying JSON config becomes corrupted, the config is discarded, and the system initiates a remediation by requesting a re-registration. It appears to be a concurrency bug causing an OS-level race condition. For whatever reason Intel Macs don’t seem to be impacted, but from what I can tell it’s an OS issues and not related to the M-series hardware.

Has anyone else seen this? Anyone have any ideas toward a fix/remediation?

This could be due to the abscense of “Rosetta”, which allows intel based applications to be installed on apple silicon. You can test this by typing in command prompt

“sudo softwareupdate --install-rosetta” then attempt to install again.