Web Run node running a REST API with authentication header

unknown

We are trying to use a Web Run node to run a vendor provided REST API that requires an authentication header. Our first Web Run node successfully receives a bearer token from the vendor. We parse the authentication data received and run a second Web Run node. The second Web Run node, which has the required "Authorization: {token}" in the header, is not working. From what we can tell, IPD is stripping the header from the call completely and for no apparent reason.

Reaching out to see if any IPA experts have seen this IPD issue before with REST API's requiring an authentication header and if they know of any fixes or workarounds.

We're running on v.10.1.1.70, but have a contact who has tried it on v.11.0.17 and it still doesn't work.

0911060553270289.pdf

russel-cornelson

The trick to setting these up is getting everything set correctly ... usually the vendor you are working with has some kind of documentation for their REST API which goes a long way. Does the token need to be base64 encoded? Is it expecting a token in the request header? request body? Json format? Does it require a POST call? a PUT call? a GET call? Seems like all these REST API's are setup a bit different, do you have documentation regarding what you need to send to the vendor?



If you have POSTMAN (chrome extension) you can usually try getting it to work; if you can get that to work but not process flow's web run open a ticket with us in support and we can assist.