How Do I? | Forum | Realisable

JSON Authentication Help (3 replies)

Colin Ash

4 years ago

Colin Ash 4 years ago

Hi, We are trying to use the JSON Reader to connect to an API.

I'm struggling with the documentation.

We already have an OAuth2 access token assigned from the endpoint provider and this is added to the authorisation header.

I have this working correctly in Postman:

curl --location --request GET 'https://api.awin.com/accounts' \

--header 'Authorization: Bearer XXXX TOKEN HERE XXXXX' \

--data-raw ''

We are using Iman version: 3.01

I'm using Basic Authentication setup as shown in the attached file.

I note that 'Bearer' is added before the auth token and wondered if this needs to be handled differently?

Rgs

Colin

https://www.realisable.co.uk/wp-content/uploads/2020/07/iman_auth.jpg

Support

4 years ago

Support 4 years ago

Colin, a couple of points:

You probably want to upgrade to the latest version of IMan. The webservices capability has significantly improved/expanded since v3 (now 4 releases behind); and each version has had significant improvemennts.
In this version you need to use OAuth vs. Basic Auth. Attached is a screenshot illustrating how this would be setup.

However, I think you will possibly struggle with this version.

https://www.realisable.co.uk/wp-content/uploads/2020/07/OAuth-Bearer-Token.png

Colin Ash

4 years ago

Colin Ash 4 years ago

Hi, Thanks for your response.

Unfortunately on my old version the 'Token Endpoint URL' is a required field and so I'm unable to get a response.

I had a feeling an upgrade might be required.

I'll look into that with our Sage VAR.

Thanks for your help

Colin

Support

4 years ago

Support 4 years ago

Colin, also this version isn't 100% TLS 1.2 compliant, so you're probably going to struggle to connect to a lot of webservices.

Username
Password

	Remember Me Lost your password? Register