Hi All, I am using the HTTP Request action in workflow to authenticate to the target application. The flow is as follows: I need to authenticate using a PAT then use credentials token from the response of that API call (This was already configured in the workflow and was working successfully when…

Hi @JackSparrow ! I was able to make it work by adding the header Accept application/json to the first HTTP Request (the one that generates the token) to output the response body to JSON instead of XML. I then used {{$.hTTPRequest.body.credentials.token}} in the next HTTP request to retrieve the toke…

Are you not receving the response from token url in JSON format. The access token can be passed in the next request. The token is accessed using {$.httpRequest.body.access_token}}. You can add a header entry with name as Authorization and value as “Bearer {$.httpRequest.body.access_token}}”

Hi @nileshnikalje , Tried {{$.httpRequest.body.access_token}} and {{$.hTTPRequest.body.access_token}} in the request header but still getting an unauthorize error.

Not sure if this would help but here is the response mapping from the HTTP Operation: [image] Here is the header that I need to put in the workflow: [image]

This is the result in the workflow logs > {"displayName":"HTTP Request","result":{"body":"66e8f6d3\"/></credentials></tsResponse>","headers":{},"responseTime":"0.509282 seconds","statusCode":200},"stepName":"hTTPRequest","task":"sp:http","technicalName":"HTTP Request"}

Are you able to get the token response via Postman? Can you share the screenshot of the Postman console for the request/respone (masking the sensitive fields)?

@jasmedina Are you trying to onboard application using web services connector? Or the issue is with the HTTP request operation in Workflows? The mention screenshots are from web services connector page.

I am configuring the HTTP request action in Workflows. I just showed my configuration in the web service connector since that once was working

Hi @nileshnikaljem, here’s the response body from Postman [image]

In Workflows I don’t think you need to capture the access token from one to other (I may be wrong). In each HTTP operation we need to define the authentication parameters in order to authenticate irrespective of previous operation.

I am getting an authentication error in the workflow step if i dont include the access token in the header

Pass the response token from one HTTP Request action to another

Identity Security Cloud (ISC) ISC Discussion and Questions

JackSparrow (Theja C) December 2, 2024, 4:04pm 12

Can you share your HTTP request config? It should look something like this

Topic		Replies	Views
Workflow HTTP Request Action - How retrieve the access token value? ISC Discussion and Questions workflows , identity-security-cloud , authentication	5	1772	July 15, 2023
OAuth2 HTTP Request in Workflow ISC Discussion and Questions workflows	3	994	February 20, 2023
IDN Workflow Http request Custom Authorization - Header Value as variable ISC Discussion and Questions apis , identity-security-cloud	3	671	March 18, 2024
Token Missing in the HTTP Request ISC Discussion and Questions workflows , identity-security-cloud	15	742	March 30, 2024
Use for variable HTTP GET request ISC Discussion and Questions workflows , identity-security-cloud	2	150	June 25, 2024

Pass the response token from one HTTP Request action to another

Related topics