yesterday
Hey,
We're trying to set up a simple Jamf Connect Notify workflow where we just want to perform a few small checks before letting the user access the desktop. To achieve this, we followed the Jamf Connect Notify Documentation: https://learn.jamf.com/en-US/bundle/jamf-connect-documentation-current/page/Notify_Screen.html.
We created a separate payload with the AuthChanger profile to set it to Jamf Connect Notify and added the key and value for the script path in the Jamf Connect Login Configuration Profile. Additionally, we created a separate package containing the script (root:wheel 700) at the path specified in the Jamf Connect Login Profile, along with two icons to brand the Notify screen. The directory used is the default one: /var/tmp/. We signed the package with the Jamf Pro Built-in CA signing certificate but also tried using a Developer Certificate and even signing the script separately before including it in the package.
Unfortunately, we keep encountering the same issue. Jamf Connect Notify appears, but only with the default screen, and it does not progress. The only way to "progress" is to cancel it using Ctrl+Cmd+X.
When inspecting the path afterward, we can confirm that the package was installed correctly and all files are in the right place. The "depnotify.log" file remains empty.
Does anyone have any suggestions on what we might be missing?