-
Notifications
You must be signed in to change notification settings - Fork 13
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
API permissions needed? #6
Comments
I am curious about this too. I have an account set up with no API access, and I can see the status of our Jamf instance. I do not have any notifications showing up though. The "Notifications" label isn't even showing in my jamfStatus menubar icon. |
I need to do some digging - looks like jamfStatus is not authenticating properly to the Jamf Pro instance. |
If there are no notifications in Jamf Pro the "Notifications" label is not displayed. Most notifications are displayed when an account has no permissions set in Jamf Pro. An example where permissions are required would be the "LDAP server configuration error" which requires read on LDAP Servers in Jamf Pro. |
See if v2.4.0 resolves the lack of notifications being displayed. |
So I can see my account I set up for this is connecting. In my Jamf Pro instance, I currently see 4 notifications listed, but still nothing showing in the JamfStatus app. If I switch to API, according to the logs it is failing to authenticate. I am 100% certain I had the correct ID and secret entered though. |
What API permissions are needed so I can create a service account with limited permissions?
The text was updated successfully, but these errors were encountered: