Hey there Paul,

Are you deploying Jamf Connect 2.45 by creating the package yourself and then pushing it via a policy? If so, you might want to consider using Mac Apps -> Jamf App Catalog instead. It simplifies deployment since it will automatically install both the helper tool and the necessary configuration profile for Jamf Connect.

This method helps ensure that the required permissions are set properly, preventing users from encountering the SecurityAgentHelper popup requesting admin credentials. If you still need to deploy it manually, you might want to check if the PPPC (Privacy Preferences Policy Control) profile is configured correctly to grant the necessary permissions for Jamf Connect.

Let me know how it goes!

In this case I downloaded the pkg and pushed that out in a policy.
I will look at the Jamf Apps method. Thank you.

A push out of the Jamf Connect App from the Jamf Apps catalogue, with Install Supporting Config Profiles checked,  fixed the issue.
Thank you @Valcovish 

I just installed 2.45 using the pkg and I didn't receive this pop-up. I know you have a solution but perhaps there's something missing in your deployment? Some more information would be helpful

We have the same problem. Does anybody know how to manually create a config profile to solve this? We have some machines where jamf connect is installed via policy instead of mac apps.

You can have more than one instance of an app in the Jamf apps section. I now have three of Jamf Connect, one for testing and the other two are for classrooms and laptops. So whilst the Jamf Apps section can only use one group for distribution, you can have the app there multiple times and send them out to different groups. All you do is rename the app when you first set it up, I simply added Classrooms, Testing and Laptops to the end of the App name.

I do not know exactly what is required in a PPPC profile to fix it with a distribution of a profile.

Having this issue with my org as well, I have a test device that is pretty much clean from any config profiles but still asks for this when I deploy the Jamf Apps version of Connect. Currently with Jamf Support to see if they are able to figure something out.

Uninstalling and reinstalling Jamf Connect does not help at all. Would appreciate to hear from you what Jamf Support is saying.

I think this is more on Apple's side. Most of our org devices use Ethernet, but there are a few setups that rely only on Wi-Fi. For the Ethernet setups, we completely disabled AirPort for Wi-Fi, and the prompt seems to only appear on Wi-Fi-enabled devices.

It turns out we also had the "Requires Admin Authorization To: Turn Wi-Fi ON or OFF" setting enabled. After turning it off, the prompt stopped appearing.

I'm currently looking into granting access to the helper via a separate PPPC to see if that resolves the issue. If not, we’ll likely disable this setting across all devices.

I can confirm that enabling the setting "Requires Admin Authorization To: Turn Wi-Fi ON or OFF" is the cause of the popup! I have disabled it, and the popup no longer appears!

Thank you very much!

So, I’m just encountering this problem myself, after having recently pushed out the Require Admin Auth to turn Wi-Fi on or off.

Ideally, I don’t want to disable that restriction. Is there another solution?

Late to party on this one. Just started deploying Jamf Connect 3.9.0 (SelfService+). Thus far, I have seen this pop-up 2 times. In both cases we isolated it to the Wi-Fi settings pane  > Advanced settings. When “Require admin...” is checked, then we see the pop-up at login window.

Jamf support confirmed there is a known PI for this (PI134880), which is tied to the network settings on an endpoint. I opened a case you can cross-reference if needed (215471224338746).
 

“If require administrator is enabled to manage network settings, it will trigger the security agent prompt on Jamf Connect 2.45+. To prevent this pop-up, we can either downgrade JC:L to version 2.44 or build a custom configuration profile with the following settings:
 

Preference Domain: com.apple.MCX
 

<?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>RequireAdminForAirPortNetworkChange</key>

<false/>

<key>RequireAdminForIBSS</key>

<false/>

<key>RequireAdminToTurnAirPortOnOff</key>

<false/>

</dict>

</plist>


Note: This profile doesn't work for me for some reason. Tested on Sequoia 15.5+ and Tahoe 26.0.1+ and got same results: The restriction isn’t persistent - users can still modify these network settings. Jamf support rep couldn't figure it out. No conflicting profiles or anything obvious. <shrug>.

I also ended up removing the Jamf Connect Wi-fi picker UI from the Jamf Connect login window, too. Its not very useful considering its laggy, doesn't support 802.1x EAP-TLS and doesn't support captive portals. However, disabling the Wi-fi picker still doesn't prevent the pop-up if “Require admin...” is enabled.

I have a recent Slack post about this topic: https://macadmins.slack.com/archives/CCWGRUFKN/p1760033835090289