Option Error at SCEP Payload

[tahir]

We have been using this profile to automatically connect to the corporate SSID. However, two days ago, I encountered an issue when I attempted to re-push the profile to a device—it failed to install.

Upon investigating the profile, I noticed an "Options" error that appears when the SCEP payload is selected. However, no specific errors are shown in the payload settings themselves. I tried to create a new profile but still error is there

Could you please assist in identifying and resolving the issue?

[whiteb]

There's talk about this on the Mac Admins Slack today. I'm seeing it myself.

It's Jamf bug/issue. I don't know if there's a PI out for it yet. I'd probably put a ticket in with support.

[Shyamsundar · Accepted solution]

its a Known issue : PI136023, Raise a case with JAMF. 

[giankenbellfore]

The "Option Error at SCEP Payload" typically indicates a misconfiguration or invalid setting within the Simple Certificate Enrollment Protocol (SCEP) payload used during device certificate enrollment. This error may arise when the profile or policy being pushed to a device contains incorrect or unsupported options, such as an invalid key size, incorrect subject name format, or mismatched certificate authority details.

Tag: ts game

[javed_apple]

I’m also encountering the same “Options 1 Error.” I’ve tried various troubleshooting methods and discovered that the same issue arises when we recreate a new profile with the same content. Consequently, Jamf has identified the problem, and they’re likely to address it in the next update.

[Jonnytiv]

We've got the same error happening with both user and computer SCEP profiles. Very annoying as all Mac users have lost their Wi-Fi connection - easy to fix but not ideal when you need to manually reconnect 100+ users.. Anything from JAMF on this one yet? 

[tahir]

I believe this will not have an impact on user's machine.

[BR_TCTX]

Same issue.  We were able to get the config profile to load on a couple mobile devices, but the request from Jamf Pro was too long.  I have a ticket open for it, but no update on when it will be resolved.

[BR_TCTX]

I'm being told that the error is just visual and doesn't actually cause an issue.  And that since we haven't whitelisted all of the new IPs, then that's why our profile isn't working. 

Not 100% sure about that answer, but it's the only one I got.  Now to convince our network team to whitelist all of those IPs, when we normally don't do so many.

[dlee_PA]

We've been pushing out new Wi-Fi profiles to supplant one with a expiring certificate but while it takes the profile it does not auto connect to the new SSID.  I have to remove the previous Wi-Fi payload to get it to auto-connect.  I thought it had something to do with the error on the SCEP payload but that's just cosmetic?

[tahir]

Thanks to all. I always love to get solutions here as this way is more fast than JAMF support.