Skip to main content

Here is my senario. We are using Casper to push a Config profile which has 3 portions inside of it.

1) CA Cert
2) User Cert
3) Network Payload - Wifi Setup

Our issue is not with 1 or 2, it is with three. If we remove the network/wifi portion of the Config it works great. But if we have add the network payload it prompts for admin creds. Now I've run a script to give user access to the network preferences in hope that this would fix the issue, but it still does not.

Does anyone have any suggestions on what might be causing this issue to arise with the admin creds.

Is your profile User Level or Computer level. Computer should not prompt for any creds.

We had it running at user level, so I changed it to run at computer level. However it still prompts for admin creds.

Also, to let you know we are using it through self service so it needs to run at the user level.

May I ask how you are deploying them through Self Service? That may be the key.

I'm taking the profile and packaging them up with composer, then adding the package to a policy. The policy executes the package once it has been downloaded from self service.

I'm thinking the command that is installing the Configuration Profile after installing it in tmp or wherever, is being run as the user. Are you running those commands with a sudo in the script?

While working on this issue I found out that there was another issue with what I was working on. Now I have to fix this one before I can tackle the issue with the wifi profile. I will update when I have a fix.

Terms & ConditionsCookie settingsAccessibility statement