Jamf Pro 11 Support

[omerninyo]

Attempting to migrate Jamf Pro 10.x to Jamf Pro 11 results in Error:
Status code: 401

[BIG-RAT]

Authentication with a local user or API client?

[BIG-RAT]

v7.2.1 should allow you to authenticate.

[sbryant82]

I'm using 7.2.2 and getting this error as well. Was working fine on jamf pro 11 already for me.

[sbryant82]

What I am seeing is that there is some issue with the toggle between using the API client /username options. On mine, when set to the client API, the username keeps appearing. Not seeing any way to delete the saved account and when trying to edit the ones that are there, it just keeps reverting.

had to do some work deleting some of the jamf migrator library files and keychain access items and keying in the API creds again and it started working.

[sbryant82]

When attempting to search for Selective Policies, I get the error "Failed to get existing policies, Status code:401". Once clicking OK, all of the policies then load in.

When attempting to run the migration on a selected Policy, receive the same error.

[BIG-RAT]

see if v7.3.0 resolves the issue.

[sbryant82]

Upgraded to v7.3.0 and the same thing is happening. it gives the error, but when clicking ok, all the results still load from the server.

I wonder if I might be missing a permission for the API, but just not sure what it would be as it did work successfully shortly after Jamf Pro 11 came out and there was an update to the app to include the client ID and Client secret.

[BIG-RAT]

Note, the existing policies it's looking for are those on the destination server, so that's the account we need to look into.
Using an API client or local Jamf Pro account?
If a local Jamf Pro account I trust there are no issues listing policies if you log into the web console or use the API from a browser.

[sbryant82]

Using the API Client

[BIG-RAT]

Finally experienced the behavior you described where the API client kept reverting a username. v7.3.1 should have that resolved.

[sbryant82]

7.3.1 is working much better. Saving of the API secrete is now working as well (never got around to posting that it wasn't). Having successful migrations now. Thank you!!

[mikem011]

I am still having this issue, even with version 7.4. However it is not with all objects. I am able to read objects from General category without issue. But if I attempt to read from macOS (i.e. Configuration Profiles or Policies) I receive the 401 error.

[BIG-RAT]

@mikem011 - What type of account (local, LDAP, API client) are you authenticating with? Getting permissions through group membership? Working with sites?

[mikem011]

I am using API Roles and Clients. No sites in this situation. Thanks!

[BIG-RAT]

@mikem011 - Curious if you've tried v7.4.2. Fixed some authentication issues, hoping yours also falls into that bucket.