Issue Description
The first login works after deploying Jamf Connect Notify, but subsequent attempts to load the login window result in a macOS loading screen that hangs indefinitely.
We need to make sure the correct login window mechanism is set when Notify is done. In the Jamf Connect Notify post-install script, we'll see an authchanger command like this:
/usr/local/bin/authchanger -reset -JamfConnect -postAuth JamfConnectLogin:RunScript,privileged JamfConnectLogin:Notify
This command uses the authchanger binary to set the login window mechanism to one specific to Jamf Connect Login:Notify. After the initial run, if this mechanism attempts to load, we'll see the indefinite macOS loading screen instead.
Troubleshooting Steps
To avoid this, we need to make sure the end of the Notify script, defined in the Jamf Connect Login configuration, contains the authchanger reset command at the very end.
Open the Notify script in a text editor.
Add the following line at the end:
/usr/local/bin/authchanger -reset -JamfConnectSave the Notify script and repackage Jamf Connect Login/Notify.
The package will now set the authchanger mechanism correctly upon completion.