Web Service Source: Passing Token from Response Header to Request Header

Identity Security Cloud (ISC) ISC Discussion and Questions
, , , ,
1

We have a source that is a Web Services connector that uses a vendor API. This API requires a generate token method to be called before anything else is done, but this method to generate the token has no response body and stores the generated token in a header that comes back with the response. This token value in the response header needs to be present as a value on the request headers for the account aggregation. Using the API in Postman we’ve seen it just manually copied over, but that won’t work for ISC. Does anyone know if this is possible using the source HTTP Operations in ISC? Thanks!

2

Custom authentication may be what you need to generate the token first as an http operation

Hope this helps

3

HI @kjerauld ,

You can take a look on the doc shared by @sk8er23. Here is the overview on how to generate access token using custom auth operation and use the generated token in other operations like account aggregation etc.,

  1. Custom Authentication.
    In response mapping, get the access token and store it in a variable

    image
    image1222×385 14 KB

  2. Test Connection (It can be any operation)
    Pass the variable from above step which has access token in the header

    image
    image1213×273 10.8 KB

Make sure you select custom authentication as authentication type in connection settings. Hope this helps!!

image
image808×138 2.31 KB

4

Hi @JackSparrow ,

Thanks for the response! I’ve tried setting up a custom authentication, but I have been running into an issue where the token is not in the body of the response and is returned as a header on the response. Do you know if it is possible to grab the value from there and store it in the access token variable?

Thanks,
Kevin Jerauld

5

Hi,
You will be able to achieve this using restClient.getReponseHeaders() to retrieve the information of headers in after operation rule.

Hope this helps

6

You could make use of BerforeOperations rule, in which you make a call to authentication API, and update the Operation request header with the access token

7

Hi @sk8er23

Thanks for the response! I was able to do this in an after operation rule. We also need to be able to do a single aggregation and get the user to aggregate off the provisioning plan native identity. Do you know if there is a way to also pass this into the after operation rule?

8

Hi @kjerauld

I’m not sure the after operation rule supports this, however the before operation rule does support provisioning plans.

Hope this helps

9

Thanks! @sk8er23 From what I am seeing I could potentially update the requestEndPoint on a beforeOperationRule and pass it to an afterOperationRule. But for some reason, the beforeOperationRule doesn’t seem to be running with the afterOperationRule attached (even if I try to make it purposely fail, it is still moving on to the after operation rule.

10

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.