Posted on 12-18-2024 01:48 PM
Has anyone managed to get around the "403 - INVALID_PRIVLEDGE" error when trying to use the API?
I created several API roles that basically give read privilege to every single thing that Jamf Pro allows you to assign read access to, then I assigned those roles to an API user.
I'm able to create the token from oath2 and use it to hit various endpoints, so I know that this user's credentials and my basic setup are correct. The API does return 200 OK codes and I get data back.
However, when I try to hit any version of the computer_prestages endpoint (v1, v2, v3) I get
Posted on 12-19-2024 07:00 AM
It does mean invalid privilege. I think (I’m on my phone rn) prestages are a different permission than computers. Double check that. If