After wiping and re-enrolling lab machines, approximately 23 out of 29 are showing the native macOS username/password login window instead of the Jamf Connect Login OAuth window. The remaining 6 machines show the correct College branded Jamf Connect login screen.
What I've confirmed on the broken machines:
- JamfConnectLogin.bundle is present in /Library/Security/SecurityAgentPlugins/
- Jamf Connect Login is fully registered in the authorization database (security authorizationdb read system.login.console shows all JamfConnectLogin entries)
- Jamf Connect Login v3.10 and Jamf Connect v3.10 configuration profiles are both installed
- A StagedPlugins folder appears in /Library/Security/SecurityAgentPlugins/ after every restart but is always empty
- No autologin configured
- A conflicting LAB: Login Window Settings profile (com.apple.loginwindow payload) was previously scoped to these machines and has since been removed but this did not resolve the issue
Has anyone experienced Jamf Connect Login silently falling back to the native login window on macOS 26 (Tahoe) specifically?
Is there a known PPPC or Security & Privacy permission required for Jamf Connect Login 3.10 to activate on macOS 26?
Is the StagedPlugins folder appearing empty after a wipe a known issue?