Leslie Helou
Leslie Helou
Using migrate dependencies I trust. That can cause package lookups, and yes every package. The reason for that is the API allows you to create multiple package records in Jamf...
Authentication with a local user or API client?
v7.2.1 should allow you to authenticate.
see if v7.3.0 resolves the issue.
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...
Finally experienced the behavior you described where the API client kept reverting a username. v7.3.1 should have that resolved.
@mikem011 - What type of account (local, LDAP, API client) are you authenticating with? Getting permissions through group membership? Working with sites?
@mikem011 - Curious if you've tried v7.4.2. Fixed some authentication issues, hoping yours also falls into that bucket.
What command line options are you using to launch the app? Using `-sourceUseClientId` and `-sourceClientId`? Note, API client info should be stored as `jamf-migrator-apiClient-` in the keychain, at least with...
I must have API client stuck on the brain, sorry for the misdirect. Try adding the following switch to help the keychain lookup: `-sourceUser ` Of course replace `` with...