3dl5q (3dl5q) asked a question.
Okta Workflow Jamf Pro API Custom Calling Card
Hi there,
Does anyone know why the Jamf Pro API custom calling card outputs 401 authorization error, and sometimes 500 null errors?
Image is not available
- TimL.58332 (Workflows)
@3dl5q (3dl5q) -- A ticket with Okta support might be able to provide some insight into the errors "If" they are occurring on the Okta side.
However, the Jamf Pro API card is built by Jamf and provided to Okta. It's why when you click the (?) help button on the card it gives you a link to Jamf's documentation on the card. How they designed it under-the-hood isn't something known to us. Those 500/401 responses could just as easily be coming from their remote server as it could be a Return Error card they used in Connector Builder to create the Jamf Pro API Connector.
Edit for clarity: If the "Card" is misbehaving or not performing an action as you would expect it to perform you would need to contact Jamf and not Okta. Okta has no visibility into the design/implementation of the card except in the most basic sense as there are minimal pieces that need to exist in Connector Builder for a connector design to be functional.
Expand Post - BrandonB.06003 (Customer)
Hard to say without knowing the API endpoint being called. usually theres a response back that would tell you why it received the error. or possible the JAMF documentation. not much on the okta side that can be done to troubleshoot
This question is closed.
@3dl5q (3dl5q) -- A ticket with Okta support might be able to provide some insight into the errors "If" they are occurring on the Okta side.
However, the Jamf Pro API card is built by Jamf and provided to Okta. It's why when you click the (?) help button on the card it gives you a link to Jamf's documentation on the card. How they designed it under-the-hood isn't something known to us. Those 500/401 responses could just as easily be coming from their remote server as it could be a Return Error card they used in Connector Builder to create the Jamf Pro API Connector.
Edit for clarity: If the "Card" is misbehaving or not performing an action as you would expect it to perform you would need to contact Jamf and not Okta. Okta has no visibility into the design/implementation of the card except in the most basic sense as there are minimal pieces that need to exist in Connector Builder for a connector design to be functional.