Custom Connector for an application that uses body to pass additional content

Help Integration Service
,
1

Hi Team,

I have a custom application for which I am building custom connector in Integration Service.
Application requires API_Key to be passed in as header - that option I get.
but it requires Username & Password to be passed within Json Body.

And it application uses POST method for authentication & returns back a token to be used in other endpoints.

Which Authentication Type should I choose for such authentication & how to store authentication token that comes back as a response.

2

@Pan_Kaj

in the connector choose basic authentication and provide your username and password

passing of key as bearer token in header will be ahndled by the custom connector internally

cheers

4

Thank you Anil for your response,

I tried with Basic Authentication by providing api key & username & password

Here is what my request header looks like for other search endpoint:

image
image1027×272 25.8 KB

  1. When I use this api using HTTP request for authentication it gives me a Authorization in “token” format, which I then use it in another endpoint as - “Bearer + token” format. Here it gives "Basic … " & I cannot change it to Bearer prefix.

With HTTP request - token is generally long. Here it is way shorter.

  1. For authentication this application does not use just the base url, they have different endpoint for Authentication which is not common or shared by other endpoints. In that case how will other endpoints share the base url which will always be different in this case.
5

@Pan_Kaj

  1. Not sure why you are adding api key here in request as it is not needed..generally apu respinse from auth is what takes care of it
  2. Did you happen to select basic auth in main connector and provide creds there?
  3. When you say a different end point is it not even the same starting of it?
  4. Also in postman how do you use it?

Cheers

6

  1. Not sure why you are adding api key here in request as it is not needed..generally apu respinse from auth is what takes care of it
    – I did not add api key here, it was automatically taken from the Basic Auth.

  2. Did you happen to select basic auth in main connector and provide creds there?
    – Yes selected basic auth and gave username & password there.

  3. When you say a different end point is it not even the same starting of it?
    – Starting of it is same upto a certain uri - but that uri alone cannot be used for authentication.

  4. Also in postman how do you use it?
    – In Postman - this application uses different endpoints for Auth & other activities, however, from starting some portion is same but for Auth it goes different from a certain point & likewise for other endpoints.

7

@Pan_Kaj

first okay I get your issue with basic auth now

basic auth by default use base64 encoding of creds and then uses it with basic

as you need for bearer..the auth itself looks different as apikey option also cannot be used as it wont send as bearer token

May I know which application it is?

cheers

8

This is CCH Axcess Workflow application. Its an accounting workflow software.