Hi fellow Appian practitioners,
I am working on an integration with an external SAP system and have run into a potential Appian shortcoming, and would like to confirm this. I first do a get request to an external system authenticating endpoint to retrieve a token. That endpoint also returns three cookies in separate headers all with identical "Set-Cookie" name. I can view them when looking at the "HTTP Response" tab in the integration object after calling the API via "Test Request":
Now, when moving over to the Result, the HttpResponse data type includes ONLY one "Set-Cookie" parameter, the last one, specifically.
I do currently need all three cookies that will be passed into the next API call, but I have no way of accessing those in the HttpResponse headers in a process model.
The integration works via Postman, as the cookies are automatically passed on to the subsequent API call. I have tried both CS with Basic Authentication as well as just the integration object(s) having basic authentication, but there is no difference in the behavior when calling the second POST API.
Has anyone seen this before where Appian ignores duplicate headers with the same name, and allows accessing only one (last one) of them?
Discussion posts and replies are publicly visible
This is because Appian translates this into a dictionary with unique field names. I think it is worth opening a support case.
Thank you for the reply. I am currently discussing with Appian via support case. While this effort is ongoing (and for short term temporary solution) would you happen to be aware of any existing plug-ins to allow accessing multiple headers?
Hi! Did you manage to find a solution for this issue? We have exactly the same issue, i.e. multiple Set-Cookie headers and the integration object only returns the last one.
Our temporary solution was/is for the time being to add an additional "management" layer (middleman) outside of our system that combines the cookies for us.
Appian proposed reviewing appmarket for suitable components, but we were not able to see one suitable for our needs. Additionally, Appian recommended building a plugin with custom plugin, but we did not resources allocated for this purpose.
We did put in a product enhancement request - if you do the same with your request, maybe they will be able to prioritize it sooner.
Great! Can you perhaps provide me with a the reference to the product enhancement request so that I can +1 the request. We will also be introducing an API gateway as an interim solution. Thanks for the quick response!
ENH 309
Hi!We are also facing the same issue. Is there any good workaround for this apart from creating custom plugin or adding middle layer?