Skip to main content
Solved

Updating Jamf Connect 2.20 OKTA users Lost Admin rights

  • February 7, 2023
  • 8 replies
  • 20 views

gabe2385
Forum|alt.badge.img+10

We are testing Jamf Connect 2.20 using OKTA and configured OIDCAdminClientID to a group of approved admin users but we noticed that when we update to a computer that had the admin user to Jamf Connect 2.20 they lost there admin rights and are not sudoer anymore as well. This has been working fine in 2.18. Seems to work fine when creating a new user but existing users they lose it.

Best answer by gabe2385

Well that was quick thanks Jamf 😂:
https://community.jamf.com/t5/jamf-connect/jamf-connect-2-20-1-now-available/m-p/283761/emcs_t/S2h8ZW1haWx8Ym9hcmRfc3Vic2NyaXB0aW9ufExEVllMOEQxWEFYMzFLfDI4Mzc2MXxTVUJTQ1JJUFRJT05TfGhL#M2615  

8 replies

mickgrant
Forum|alt.badge.img+12
  • Contributor
  • 146 replies
  • February 7, 2023

I am also experiencing this issue


Forum|alt.badge.img+7
  • Contributor
  • 16 replies
  • February 8, 2023

We are also seeing this across environments. I have reported this as well. 

 


Forum|alt.badge.img+5
  • Contributor
  • 33 replies
  • February 8, 2023

Yip, can confirm the same for me on 13.2 Ventura, I am an admin, and upgraded mine from 2.19 to 2.20 to test and now I have lost admin rights


Forum|alt.badge.img+1
  • New Contributor
  • 4 replies
  • February 8, 2023

Experiencing the same issue on Mac m1 and intel running 13.2 and 2.20 distributed via Jamf Pro.


Forum|alt.badge.img+7
  • Contributor
  • 16 replies
  • February 8, 2023

The issue appears to occur if the RedirectURI is not set to jamfconnect://127.0.0.1/jamfconnect

https://127.0.0.1/jamfconnect should work but its not on 2.20. Feedback has been submitted


gabe2385
Forum|alt.badge.img+10
  • Author
  • Valued Contributor
  • 59 replies
  • Answer
  • February 8, 2023

gabe2385
Forum|alt.badge.img+10
  • Author
  • Valued Contributor
  • 59 replies
  • February 8, 2023

Forum|alt.badge.img+1
  • New Contributor
  • 4 replies
  • February 8, 2023

Resolved with 2.20.1 here as well