Jamf Connect Login doesn't show on Reboot

anadeem
New Contributor II

Hello! Trying to polish up our Jamf Connect configuration, but I notice upon reboot the Jamf Connect screen doesn't pop up, I have Filevault disabled, and I made it so the authchanger script runs every time the computer logs in. This is the plist file:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>CreateJamfConnectPassword</key>
<true/>
<key>CreateNewUserHide</key>
<true/>
<key>DemobilizeUsers</key>
<true/>
<key>DenyLocal</key>
<true/>
<key>DenyLocalExcluded</key>
<array>
<string>orgadministrator</string>
</array>
<key>EnableFDE</key>
<false/>
<key>EnableFDERecoveryKey</key>
<false/>
<key>LocalFallback</key>
<false/>
<key>LoginWindowMessage</key>
<string>Welcome to xyz! Please log in with username@company.com and password.</string>
<key>Migrate</key>
<true/>
<key>OIDCClientID</key>
<string>client id</string>
<key>OIDCHideRestart</key>
<false/>
<key>OIDCIgnoreAdmin</key>
<false/>
<key>OIDCProvider</key>
<string>EntraID</string>
<key>OIDCROPGID</key>
<string>more ids</string>
<key>OIDCRedirectURI</key>
<string>https://127.0.0.1/jamfconnect</string>
<key>OIDCTenant</key>
<string>tenant id here</string>
<key>OIDCUsePassthroughAuth</key>
<true/>
<key>ROPGProvider</key>
<string>EntraID</string>
<key>ROPGTenant</key>
<string>tenant id here</string>
</dict>
</plist>

1 ACCEPTED SOLUTION

anadeem
New Contributor II

I realized why it wasn't working! The FileVault login screen appeared before Jamf Connect Login, since it was enabled via policy check in and not through the plist file from Jamf Connect.

View solution in original post

2 REPLIES 2

Mattdjerome
New Contributor III

This happened to me a while back. I had not installed the launchagent. Make sure that's running as well.

anadeem
New Contributor II

I realized why it wasn't working! The FileVault login screen appeared before Jamf Connect Login, since it was enabled via policy check in and not through the plist file from Jamf Connect.