Hi all,

Am seeing Error 405 Method not allowed with my SCEP payload. Anyone has seen the error before?

Thanks

hi @khey did you ever find out why this was happening as we are seeing the same thing.

Hi @khey ,

Did you find a solution to this problem already?

Thanks!

Any news?

I had a similar issue with the AD CS connector. I went to the certificate server, opened server manager, clicked on tools and opened Certificate Authority. In there I was able to see the failed request. I discovered it was my subject name giving error then my template was wrong. Once I fixed those, it was able to deploy the configuration profile.

@Tigerhaven ,@d.svejda ,@Eigger Sorry all. Wasnt aware that there were responses.
First under Jamf Pro URL, remove any entry inside "JAMF PRO URL FOR ENROLLMENT USING BUILT-IN SCEP AND IPCU"
Secondly, under the SCEP Server IIS HTTPS binding, ensure you bind the right certificate.

Not sure if this will help or not. Using SecureW2 as our vendor and Active Directory.
We went through this last year. Took for.ev.ah. to get it working. Lots of trial and error and many hours on the phone with SecureW2 and our network guys.
Anyway, now that its working for us, one thing I note that's different between my config and yours is the formatting of the content in Subject Alternative Name Value.

In my config we use different separators (though its entirely possible this is either vendor specific or makes no difference whatsoever);
$EMAIL;;$COMPUTERNAME;$UDID;$EXTENSIONATTRIBUTE_25

Note; the double ;; is intentional.
also note; $EXTENSIONATTRIBUTE_25 is the LDAP attribute variable, capturing our assigned user AD UUID.

@pbenware1 Using SecureW2 as well and just stared having this problem - <NSOSStatusErrorDomain:-67701>. What was the fix for you?

@caitlin.mabe for us it was because the computer record didn't have a username associated with it in Jamf, so there was no user to put in the certificate to identify the user.

Hope you got this figured out before now! :)

What was the fix for this?