Rest Job-Steps, OAuth2, Misc.

For the job steps RestGet, RestGetHandleDocument, RestPush, and RestPushHandleDocument, you can configure the following settings under “Element Properties” in the “Advanced” section:

• The direction of the created, the received message,
• the system partner of the created message,
• the trading partner of the created message, and
• the authentication method to be used.

The following OAuth2 Bearer authentications are supported:

• OAuth2 Bearer (x-www-form-urlencoded):
  • HTTP Post,
  • Content type application/x-www-form-urlencoded,
  • body “grant_type=client_credentials&client_id=<Client ID>&client_secret=<Client Secret>” and
  • additional body headers that can be defined in the job step.
• OAuth2 Bearer (Authorization header):
  • HTTP Get,
  • Base64-encoded with the username and password in the Authorization header, separated by a colon.
• OAuth2 Bearer (Authorization header + grant_type body):
  • HTTP Post,
  • Content type application/x-www-form-urlencoded
  • Base64-encoded with the username and password in the Authorization header, separated by a colon and
  • body “grant_type=client_credentials”.
• OAuth2 Bearer (JSON body):
  • HTTP Post,
  • Content type application/json
  • body: { “username”:<Client ID>, “password”:<Client Secret> }

The returned Bearer token is read from a JSON or XML object, or directly at the top level.

• In the XML, from the AccessToken, SessionToken, or AuthToken element.
• in JSON from:

   { "token":"..."}, { "accessToken":"..."} , { "access_token":"..."} , { "sessionToken":"..."} 

  oder unter data mit den zuvor genannten Tokens:

    { "data": { "token":...} }, { "data": { "accessToken":...} }, etc.  

This setting determines how the bearer token should be passed when the request is made:

• in Authorization-Header or
• as URL parameter.