Hello everyone
Pretty new to jamf so please excuse me.
We are in the process of using jamf connect to elevate access currently still testing.
I had one test machine that was running 2.34 elevated access was working i had about ~3minutes left of admin access, then our jamf connect policy decided to trigger (upon checkin) and upgraded to 2.35. All the sudden the request admin button via jamf connect does nothing. I checked 2 other macs that were running 2.35 and both are experiencing the same, requesting admin rights does nothing.
Opening jamf connect to collect logs, I see one error that stands out
Process: Jamf Connect, Category: PrivilegeElevation, Contents: Elevation failed, role base elevation is active but OIDCAdminAttribute is not set
And this is where it gets weird for me, initially our OIDCAdminAttribute was set to role
After it broke, jamf support told me is incorrect and to change it to either groups or roles & to delete the jamf connect state plist every change role>groups>roles. However, none seem to work so i removed OIDCAdminAttribute entirely but still receive the same error
Process: Jamf Connect, Category: PrivilegeElevation, Contents: Elevation failed, role base elevation is active but OIDCAdminAttribute is not set
I'm currently still talking with support to figure out but every and all help would be useful
Thank you!