Hello,

I'm currently working on a mass deployment of Jamf Connect Login for Azure. The primary goal is to demobilize accounts on a mass scale. However, I am keen on ensuring that this deployment process is as silent and non-disruptive to our users' workflow as possible.

Here's what I have for my current .plist configuration for Jamf Connect Login:

<?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>AllowNetworkSelection</key>
<true/>
<key>CreateNewUserHide</key>
<true/>
<key>CreateJamfConnectPassword</key>
<true/>
<key>LicenseFile</key>
<data>*license key value*</data> 
<key>OIDCAdminAttribute</key>
<string>roles</string>
<key>OIDCClientID</key>
<string>*client_id*</string>
<key>OIDCNewPassword</key>
<false/>
<key>OIDCProvider</key>
<string>Azure</string>
<key>OIDCROPGID</key>
<string>*client_id*</string>
<key>OIDCRedirectURI</key>
<string>https://127.0.0.1/jamfconnect</string>
<key>OIDCTenant</key>
<string>*tenant_id*</string>
<key>OIDCUsePassthroughAuth</key>
<true/>
<key>DenyLocal</key>
<true/>
<key>DenyLocalExcluded</key>
<array>
<string>helpdeskv2</string>
</array>
<key>LocalFallback</key>
<true/>
<key>Migrate</key>
<false/>
<key>MigrateUsersHide</key>
<array>
<string>helpdeskv2</string>
<string>jamf_manage</string>
</array>
<key>DemobilizeUsers</key>
<true/>
<key>OIDCAdmin</key>
<array>
<string>Administrator</string>
</array>
<key>CreateAdminUser</key>
<true/>
<key>OIDCIgnoreAdmin</key>
<true/>
</dict>
</plist>

In my testing, I managed to prevent the Jamf Connect login window from popping up every time a user logs in. However, I found that Jamf Connect did not start at all after the login. Is there a way to ensure that Jamf Connect runs silently in the background, without a need for the login prompt, while still functioning as expected?