Reltio Connect

 View Only

 Token Generation API is not working through Reltio custom action in RIH recipe

  •   Reltiointegrationhub
  •   RIH
Utsa Das's profile image
Utsa Das posted 11-23-2022 11:51
Hi All,

Through Reltio custom action in RIH recipe other POST call  is working but the API for token generation is always throwing error .Can anyone help here to resole the same ?
Sheshadri V's profile image
Sheshadri V
Hi Utsa Das,

Can you provide more clarity and brief about what you are trying to achieve.
It will be great if you can have API call and the scenario to better assist you.
Utsa Das's profile image
Utsa Das
Hi,

I am trying to call below API from custom action of reltio call :-

http://auth.reltio.com/oauth/token?username={{login}}&password={{password}}&grant_type=password


and in output I want to catch the output token ,but it is always giving me error that  "Full authentication is required to access this resource" where the Authorisation details are correct and have all the permission in Reltio is working perfect well from postman.
Sheshadri V's profile image
Sheshadri V

Hi Utsa Das,

 The hassle of getting token and using in next steps is eliminated by RIH(via App Connectors/HTTP Connector).

For Reltio you can have Reltio Connector and use Custom API without need of token for others you can use HTTP Connector with appropriate credentials like OAuth, Username password, Client credentials etc.

Just wanted to understand the next step after you get TOKEN as you will be calling an Reltio Custom API and that can be achieved by Custom Action of Reltio Connector. 

So, there is no need to get Token and use in further steps at least for Reltio API’s.

Utsa Das's profile image
Utsa Das
Hi ,

Thanks for your answer .I was actually trying to create a recipe for add/update the L3 config and to call the config API I was trying to use HTTP connector as through Reltio custom action the input was getting very big and in HTTP connector i can give the full L3 xml  as input.

Now I was getting Access error every time through HTTP so was thinking to explicitly give the token to HTTP connector at the time of call.
Gino Fortunato's profile image
Reltio Employee Gino Fortunato
Generally, the full authentication error is received when the header part is missing from the API call. Try adding the header information and see if it works.
Utsa Das's profile image
Utsa Das
Hi Gino,

I have added the header part but still it is failing with the same error.

The below is the input detail for the custom action recipe :-

{
response_type: json,
path: https://auth.reltio.com/oauth/token?username=<Username>&password=<Password>&grant_type=password,
input:
{
schema: []
},
output: [],
request_headers:
[

{
name: Authorization,
value: Basic <Value>
}
],
request_type: json,
Action name: Custom action,
Method: post
}

And the error I am getting always is :-

401 Unauthorized: {"error":"unauthorized","error_description":"Full authentication is required to access this resource"}


With the same credentials I can do everything from postman/UI.


@Sheshadri V,

I am actually try to create a recipe for L3 configuration change where I need to pass the L3 json and then it will deploy the same in the respective environment.

Sheshadri V's profile image
Sheshadri V
Hi Utsa,

Here is sample Using Reltio Custom Action of Get L3 Configuration.


Once I have L3 I can make respective changes and then Post back using PUT option.


All this is possible using Reltio Connector and Custom Action
I still feel there is no need for HTTP Connector.

Gino Fortunato's profile image
Reltio Employee Gino Fortunato
thinking this through a bit more, shouldn't you be using the 'Connection' to reach the tenant vs. explicitly getting a token?