AD Certificate Payload Failure

ManuelC
New Contributor

Dear All,

First of all would like to thank in advance any help or advise regarding this.

 

To put you all in a little bit of context on our environment we are using a Configuration Profile including "AD Certificate" Payload and Network Payload to configure the connection via TLS Auth.

We have been working for a while with this type of configuration without the need of binding our Mac fleet to AD , and indeed we are using Enterprise Connect (yes, I know this is kinda deprecated and we should be using like Kerberos SSO), so far this allowed us to get the AD Certificate (User Level Certificate) Payload in the past without any issue. So far since like 1 week ago it suddenly stopped working, So still figuring out what changed or if there was a change that I didn't get informed on our Infrastructure. We want to avoid any open external traffic like going through workarounds as SCEP > or any AD CS Connector...

Would now to request your assistance , if at any point you have configured something like this. Or what could be the reason behind it suddenly stopped? I'm thinking more of a CA Server Permission to access the necessary template, but pretty unsure as I do not currently manage this thing and not sure what type of permissions should be set on that part. 

Back again any advise would be gladly appreciated.

2 REPLIES 2

howie_isaacks
Valued Contributor III

Can you provide screenshots of the configuration profile payload and screenshots of the failures you see?

jtrant
Valued Contributor

Check the logs on your AD CS Connector and look up any error codes in Microsoft's support pages. You can also post them here.