Issue Summary

If an Adapter Job is ran with a JAMF Adapter, and the account used to authenticate to JAMF has a special character in the password, it will fail with a 401 Unauthorized Error, because it can't get the token.

Steps to Reproduce

1. Create Assets Data Manager JAMF Adapter with a JAMF account that has a special character in the password.
2. Run Job configured for said Adapter.

Expected Results

It works and the data is pulled, as normal.

Actual Results

Error is returned instead:

Failed to execute the job.

Error in requesting a token: {
"httpStatus" : 401,
"errors" : [ ]
} 

Workaround

Use a JAMF account without a special character in the password.

OAUTH Authentication has now been added to the jamf adapters (https://support.atlassian.com/assets/docs/data-manager-jamf-adapter/).