Versions Compared

Old Version 6

changes.mady.by.user user-45924

Saved on

compared with

New Version Current

changes.mady.by.user jtel Support

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Sv translation
languageen

SalesForce Account

First of all, verify that the SalesForce Account works, by logging in. 

If necessary, a verification token must be entered (this happens on each new browser you login to). 

Recommend: when asked by SalesForce, input a mobile number as this speeds the process up considerably in the future.

...

(warning) Please note: the relevant Salesforce Account password for the jtel API should not contain some special characters (e.g. "< ) but may consist of a long sequence using alphanumeric characters.

Reset Security Token

If the account is new, the security token must be reset.

In the top navigation, go here:

Image Modified

Then on the left, here:

Image Modified

Then click "Reset Security Token".

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
titleCURL - Generate OAUTH Token
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
titleCURL - Generate OAUTH Token Response
{"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:

...

Sv translation
languagede

Status
colourRed
titleThis page is only available in English

Sv translation
languagefr

Compte SalesForce

Tout d'abord, vérifiez que le compte SalesForce fonctionne, en vous connectant. 

Si nécessaire, un jeton de vérification doit être saisi (cela se produit à chaque nouveau navigateur auquel vous vous connectez). 

Recommandation : lorsque SalesForce vous le demande, saisissez un numéro de téléphone portable car cela accélère considérablement le processus à l'avenir.

Réinitialisation du jeton de sécurité

Si le compte est nouveau, le jeton de sécurité doit être réinitialisé.

Dans la navigation supérieure, allez ici :

Image Added

Puis à gauche, ici :

Image Added

Cliquez ensuite sur "Réinitialiser le jeton de sécurité".

Le nouveau jeton de sécurité sera livré par Email.