Target API Client returns 403 error

[ckemp19]

Trying to replicate pkgs to a new Jamf Cloud instance. jamfcpr connects to our production cloud just fine, but the same credentials return a 403 error when connecting.

I have an API client with full write permissions that had been used successfully today with jamf-migrator, that failed with jamfpcr. I tried rotating the credentials, same issue; subsequently updated the password in migrator & it connected, so it appears to be an issue with jamfcpr. Verified that the connection between Jamf and the Cloud Distribution point is working.

LMK if there's some debugging I can provide.

[hooleahn]

Same here. Seeing this in the logs:

20241203_163219 [ListPackages.jcdsVersion] Unable to retrieve data from the JCDS on https://myinstance.jamfcloud.com.
Status code: 403

EDIT: I fixed my issue. In my case I had to rotate the credentials. I wish Jamf would indicate that you need to do that after adding another role to the API Client.

[BIG-RAT]

Are credentials saved in the keychain? If so can you verify they saved correctly?
Should be able to locate them by searching passwords for JPMA-

[ckemp19]

I only see the credentials for the source, not the target

[BIG-RAT]

If you haven't yet tried, hit the edit button for the destination server and re-enter credentials, enable save and check the keychain. Let me know how things look as time permits.

[ckemp19]

I had done that before - deleting the credentials & trying to re-add them, but it didn't take. Today I rotated the credentials again and re-entered the information and this time it decided to work...

Replication in progress.

[BIG-RAT]

Thanks for the quick response.

And ya, there are some gremlins in the app that need flushing out.