...
The new security token will be delivered by E-Mail.
Generate OAUTH Token
To use REST Services, an OAUTH Token must be generated by SalesForce.
See https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_understanding_username_password_oauth_flow.htm for a reference.
The customer will provide the following information:
- client_id
- client_secret
The OAUTH Token is generated using CURL.
| Code Block | ||
|---|---|---|
| ||
curl -d "grant_type=password&client_id=<client_id>&client_secret=<client_secret>&username=<salesforce_user_name>&password=<salesforce_password><security_token>" -X POST https://login.salesforce.com/services/oauth2/token |
NOTE: there is no space between <salesforce_password> and <security_token>
For the endpoints, use the following for the live system:
https://login.salesforce.com/services/oauth2/token And the following for the test / sandbox system:
https://test.salesforce.com/services/oauth2/token The following shows a sample response received from the SalesForce system:
| Code Block | ||
|---|---|---|
| ||
{"access_token":"00D9E0000000ZGl!AQoAQATcoQIashdlkjhkerwjC87giIs5umhHmQA_xWbb4qqM2t1asdaSXrUs8J.WXmCRQr2K93FydCd4y4qdG7zOmGC0LgDxEDJEDpf4n7AiygkS","instance_url":"https://cs88.salesforce.com","id":"https://test.salesforce.com/id/00D9AAE000000AAAA0ZGlUAM/0059E000002GhnoQAC","token_type":"Bearer","issued_at":"1510758069682","signature":"WKXl67nbYAAg+CeqU+eekp4AFDsasdasdarabctz1xmBN7DD7kcw="} |
The access_token field is required in the JTEL system, together with the instance URL, which forms the base of the SalesForce jtel REST API Base URL in the jtel Portal.
The following shows an example of the finished URL configuration in the jtel System:
