When using the Jamf Pro Classic API connector in Okta Workflows, selecting the Device Lock or Erase Device command on the Send Computer MDM Command card returns the following error:
400 Bad Request
This issue occurs because Jamf deprecated these commands in the Classic API. Resolve this error by using the Jamf Pro API connector instead to send the Mobile Device Management (MDM) command.
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Okta Workflows
- Jamf Pro Classic API Connector
Jamf deprecated the Device Lock and Erase Device commands for the Classic API. For more information, review the Jamf Pro 11.2.0 Classic API Removals documentation.
How is the 400 Bad Request error resolved for Jamf Pro MDM commands?
To send the Mobile Device Management (MDM) command to the desired device, use the Jamf Pro API connector instead of the Jamf Pro Classic API connector. The Jamf Pro API connector supports the updated commands and does not generate the 400 Bad Request error. Reference the links in the Jamf Pro API connector documentation for assistance with sending the MDM command to the desired device.
NOTE: The Jamf Pro API connector is a third-party connector maintained by Jamf.
