Closed tempusthales closed 11 months ago
BIG-RAT
commented
1 year ago I'll poke around a bit. This is what I have for my API client and am able to log in and list policies.
If you have policies without a custom trigger adding the Update Policies would be needed for generating the script.
dan-snelson
commented
1 year ago In a single test against Jamf Pro 11.1.0-b1, SYM-Helper 0.8.3-b2 worked as expected for me.
tempusthales
commented
1 year ago will try it on 11.0 and let you know..
On Fri, Oct 27, 2023 at 5:08 AM Dan K. Snelson @.***> wrote:
In a single test against Jamf Pro 11.1.0-b1, SYM-Helper 0.8.3-b2 worked as expected for me.
— Reply to this email directly, view it on GitHub https://github.com/BIG-RAT/SYM-Helper/issues/16#issuecomment-1782651388, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASVPR2VBMHVAAXYAECE5DTYBOB2DAVCNFSM6AAAAAA6P646AKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBSGY2TCMZYHA . You are receiving this because you authored the thread.Message ID: @.***>
-- Gilbert J. Palau @.*** http://gilbertpalau.com
Describe the bug After Launching SYM-Helper 0.82 (but this also happened before), if you are using API Roles and Clients, you get a pop up that reads No policies found. Veriry the account has appropriate permissions to read policies.
If a regular user account is used, this error doesn't happen. I was able to connect and properly.
To Reproduce Launch SYM-Helper and try to log in with an API Client.
Expected behavior Expected behavior should be that you log in with said credentials and the policies should be read into the client.
Code/log output Dan Snelson reproduced this on https://macadmins.slack.com/archives/C04FRRN3281/p1698262456927419
Screenshots Screenshot 1
Environment (please complete the following information):
Additional context This issue started occuring since before SYM-Helper 0.8.2, but after we migrated to 11.0 on our test environment