The issue appears to occur if the RedirectURI is not set to
jamfconnect://127.0.0.1/jamfconnecthttps://127.0.0.1/jamfconnect should
work but its not on 2.20. Feedback has been submitted
Did you ever get anything figured out on this? my
com.jamf.connect.state.plist files are not pulling the Okta groups
either and I'm trying to scope based on group membership as well.
So I wonder if this supposed “fix” is specific to Azure and those URL’s,
because I’m using Okta and will probably have different results. I’ll go
through those steps with the Okta URL’s and see what happens. For now
I’ve just been downgrading to 2.7....
I don't understand why this isn't being implemented into the Patch
Management section where we can control who gets what version of the app
(Early Adopters vs All). With this new App Installers, you have a choice
of all clients or all servers. This s...
