Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for token auth in jamf #396

Closed
headmin opened this issue Mar 16, 2022 · 0 comments · Fixed by #397
Closed

Support for token auth in jamf #396

headmin opened this issue Mar 16, 2022 · 0 comments · Fixed by #397

Comments

@headmin
Copy link
Collaborator

headmin commented Mar 16, 2022

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant