About david_halsband4

david_halsband4

There are different ways how to authenticate within a REST call in Process Integration. Especially when calling a REST API it is more and more common to use OAuth 2.0. Unfortunately the standard REST adapter so far only supports some types of OAuth 2...

david_halsband4

Hi Rashmi, you can write the TOKEN value after the mapping-lookup into the ASMA fields, which you can use as a configurable parameter. Then you don't need a TOKEN field in your target structure. Best regards, David

david_halsband4

Hi Navneet, I am using an online base64 encoding tool. Encode 'apitoken:<APITOKEN>, e.g. apitoken:8CUjyOBmSOXkBWS7cAsjuaeKnZT5YG3VQKra7kSy Copy result, e.g. YXBpdG9rZW46OENVanlPQm1TT1hrQldTN2NBc2p1YWVLblpUNVlHM1ZRS3JhN2tTeQ== Go to your HTTP ...

david_halsband4

So does it mean that the API token call works? Can you see the token in the log?

david_halsband4

I have never used NTLM, so I cannot give you any hints here.

david_halsband4

Sorry, no idea. Please try it out.

User Statistics

User Activity

OAuth 2.0 authentication within a UDF mapping to be included in REST receiver channel

Re: OAuth 2.0 authentication within a UDF mapping to be included in REST receiver channel

Re: OAuth 2.0 authentication within a UDF mapping to be included in REST receiver channel

Re: OAuth 2.0 authentication within a UDF mapping to be included in REST receiver channel

Re: OAuth 2.0 authentication within a UDF mapping to be included in REST receiver channel

Re: OAuth 2.0 authentication within a UDF mapping to be included in REST receiver channel