You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jamf has documented API change towards token auth here. Onwards from version 10.35.0 of Jamf Pro, the Classic API now accepts Bearer Token authentication. Tokens can be obtained from the Jamf Pro API using the /v1/auth/tokens endpoint.
For the Jamf Pro API, here’s what’s required for authentication:
Multi-step process involving multiple API calls
Username and password only used to get authentication token(Bearer Token). The Bearer Token is subsequently used for authentication
Username and password must be base64-encoded
Bearer Tokens are valid for 30 minutes maximum
Introduces need to validate authentication Bearer Tokens before making API calls
The text was updated successfully, but these errors were encountered:
Jamf has documented API change towards token auth here. Onwards from version 10.35.0 of Jamf Pro, the Classic API now accepts Bearer Token authentication. Tokens can be obtained from the Jamf Pro API using the /v1/auth/tokens endpoint.
For the Jamf Pro API, here’s what’s required for authentication:
The text was updated successfully, but these errors were encountered: