Jamf Pro rarely operates in a vacuum. For most IT admins, it's one part of a much larger ecosystem that might include identity providers, security tools, network infrastructure, SIEMs, certificate authorities, automation platforms and plenty of other services.
Fortunately, Jamf provides several ways to connect those systems. Having spent a good portion of my career working with Jamf integrations, I've found that the more useful question often isn't "Does Jamf integrate with this?" but "What information needs to move between these systems, and what tools do I have to make that happen?"
APIs answer questions. Webhooks start conversations
Two of the most useful tools for answering that question are APIs and webhooks.
The Jamf Pro API is the modern REST API for interacting with Jamf Pro, with an expanding set of resources and support for things like JSON, filtering and pagination. The Classic API has been around much longer and still provides access to resources that many integrations rely on. Depending on the workflow you're building, you may find yourself using one or both.
APIs work well when another system needs to ask Jamf a question: What do you know about this Mac? Which group does it belong to? What does its inventory look like?
Webhooks work in the other direction. Instead of another service repeatedly checking Jamf to see if something happened, Jamf can tell that service when it happens.
This gets especially useful when APIs and webhooks are used together.
Connecting MDM, PKI and network access
Certificate-based network access is a good example because it touches several systems that don't always get thought about together.
SecureW2's integration with Jamf Pro uses both APIs and webhooks at different points in the certificate and device lifecycle.
Take certificate enrollment using Dynamic SCEP. Jamf Pro's SCEPChallenge webhook can request a unique challenge from an external service when a managed device needs a certificate. When SecureW2 receives that request, it uses Jamf's APIs to look up and validate the device before returning the challenge.
The flow looks roughly like this:
Device → Jamf Pro → SCEPChallenge webhook → SecureW2 → Jamf API → SCEP challenge → Certificate
That means Jamf isn't just responsible for delivering the configuration that requests a certificate. The device information already available in Jamf can also help determine whether that request should be trusted.
And there's no reason that context has to stop being useful once the certificate is issued.
When the device later connects to an 802.1X network using that certificate, Jamf can again provide context about the device. A policy engine can look up information such as Smart Group membership via API and use it as another input when deciding what network access to provide.
For example, a Smart Group that defines device compliance could influence whether a device receives normal network access or is placed onto a remediation network.
But what happens if a device's state changes after it's already connected to the network? That's another opportunity for webhooks. Jamf Pro's SmartGroupComputerMembershipChange webhook can notify an external service when a device enters or leaves a Smart Group. If that group represents your organization's definition of compliance, the receiving service can respond accordingly, whether that's revoking a certificate or triggering a change in network access.
Think beyond the individual integration
Network access is just one place this approach can be useful. Jamf APIs and webhooks can provide similar connections to identity platforms, security products, automation tools, SIEMs and other services.
The important part is figuring out what information needs to move between the systems, who has that information, and when it needs to move.
So instead of starting with "Does Jamf integrate with this?", I tend to start with three questions:
What information do I need? Where does it live? What should trigger the exchange?
Answer those, and you may find that Jamf already provides the pieces you need to build the integration.
