Security

I'm investigating adding JAMF as an endpoint context server to our ClearPass environment to help identify JAMF managed Macbooks.

While adding our JAMF server I've run into some issues with it being able to poll.  I've verified the URL is correctly entered, routing to/from the JAMF server works, DNS queries work, and that the user/pass I enter is correct.  I'm unfortunately still getting a 401/404 error no matter what I do.  The JAMF server doesn't even see an attempt coming in from the ClearPass ip address, though it does see my successful logins/failures from my laptop.

I noticed after adding the Endpoint Context Server that there are also dictionary methods which can be applied to these objects.  One of those is related to JAMF.  I am unsure whether any JAMF related dictionary methods have to be added - can anyone confirm whether it can get by with just being added as an Endpoint Context Server, or what the use case for additional dictionary methods would be?

I've also been having weird enpoint context server problems over the last few months with the last few versions of Clearpass. This includes both to JAMF and to Google Admin Console. It seems to sync sometimes and/or somewhat, but doesn't sync to either systems completely anymore. It seems others are having this issue based on the release notes.

Yeah I'm seeing WARN level errors where it never seems to fully sync:

In regards to the dictionary methods for JAMF, these are actually just API calls to the JAMF server.  You can define more specific actions using context server actions such as DELETE, POST, GET, PUT.  Obviously beware when playing around with anything but a GET.

Is this a Clearpass software problem, or has the process changed and the documentation not been updated? I started having issues in like 6.6.8 I think and it has continued to the newest most current version as of today. It was syncing AT ALL in a short lived 6.7 version.