Splunk Cloud Platform

JAMF Pro Add on for Splunk

skseifert
Engager

we are looking to confirm with the "JAMF Integrations" that this app supports the Jamf Pro API vs Classic API and that it was configured to use the API Roles and Clients with the Access Token, Client ID and Client Secret vs Basic Auth

Labels (2)
0 Karma

marnall
Motivator

It appears that the JAMF classic API uses the paths:

https://server.name.here:8443/JSSResource
https://server.name.here:8443/api

While the JAMF Pro API uses the paths:

https://server.name.here:8443/uapi

There are mentions of the uapi endpoint in the file in the "JAMF Pro Add on for Splunk" app at /JAMF-Pro-addon-for-splunk/bin/uapiModels/devices.py and jamfpro.py in the same directory, so likely the app does use the Pro API as well as the classic API.

However the code for jamfpro.py suggests that it uses basic authentication with username and password to obtain a bearer token, with no mention of Access Token, Client ID, or Client Secret. Thus it is likely the answer to your question about authentications is that the app only supports basic authentication.

 

 

class JamfPro:
    class JamfUAPIAuthToken(object):
    
    ....
    
        def get_token(self):
            url = self.server_url + 'api/v1/auth/token'
            logging.info("JSSAuthToken requesting new token")

            userpass = self._auth[0] + ':' + self._auth[1]
            encoded_u = base64.b64encode(userpass.encode()).decode()
            headers = {"Authorization": "Basic %s" % encoded_u}
            for key in self.extraHeaders:
                headers[key] = self.extraHeaders[key]

            response = self.helper.send_http_request(url="https://" + url,
                                                     method="POST",
                                                     headers=headers,
                                                     use_proxy=self.useProxy)
            if response.status_code != 200:
                raise Exception
            self.unix_timestamp() + 60
            self._set_token(response.json()['token'], self.unix_timestamp() + 60)

 

0 Karma
Get Updates on the Splunk Community!

Splunk Observability Cloud’s AI Assistant in Action Series: Analyzing and ...

This is the second post in our Splunk Observability Cloud’s AI Assistant in Action series, in which we look at ...

Elevate Your Organization with Splunk’s Next Platform Evolution

 Thursday, July 10, 2025  |  11AM PDT / 2PM EDT Whether you're managing complex deployments or looking to ...

Splunk Answers Content Calendar, June Edition

Get ready for this week’s post dedicated to Splunk Dashboards! We're celebrating the power of community by ...