jamf
Replicator only works in debug mode
If I launch the replicator from the /Applications folder, every attempt to replicate any items is met with a 405 error. But if I launch the replicator via the terminal using.
sudo /Applications/Replicator.app/Contents/MacOS/Replicator - debug.
The replicator will work normally.
Go ahead and grab v8.0.1.
Wonder if you could launch the app as such:
/Applications/Replicator.app/Contents/MacOS/Replicator | grep apiCall | tee -a ~/Desktop/Replicator-apiCalls.log
Be helpful to look at the log off the Desktop as well as the log in ~/Library/Containers/com.jamf.jamf-migrator/Data/Library/Logs/Replicator/
I downloaded and used 8.0.1 and tested it as is. I had the same issue: the 405 error. I relaunched with the requested command and had the same issue. The logs are attached.
Your destination server doesn't appear to be a Jamf Pro server. Note, the API does not utilize SSO.
Still puzzled how it would work when launched via command line.
So, it appears the replicator is replacing my test environment user with our Okta preview URL, but not when launched via the command above. I wonder if there is some miss-configuration on my test environment end or in our Okta preview setup. I will double-check everything and then re-test.
I can't see how Replicator is changing what's been entered for the destination. No checks for a redirect, CNAME, or anything else like that is performed.