Integration returns a http Response with redirect with header parameters. I want to call this from an interface via link or button within appian.

If you are making a GET request, is there a reason why that request cannot be a direct link? The response is a 302 so the browser should handle the redirect just fine. If it is not a GET request, or for some other reason you cannot insert the URL directly into the link component, you will have to wrap the call into a web api object, i.e. your web api will make the integration call and pass the location header as part of a 302 response. Your interface has a link to the web api.

If you are making a GET request, is there a reason why that request cannot be a direct link? The response is a 302 so the browser should handle the redirect just fine. If it is not a GET request, or for some other reason you cannot insert the URL directly into the link component, you will have to wrap the call into a web api object, i.e. your web api will make the integration call and pass the location header as part of a 302 response. Your interface has a link to the web api.

it does a post.

So i have the post integration wrapped in a webapi.... where I translate the response out of the web api.

I tried directly using the response out of the web api but it didnt like that.

Looks like I may have to process the pieces and try returning that way.

I get the message Set-Cookie can not be set by WEB API. It seems this will be critical because it is essentially authorizing the user.
Any suggestions?

Thank You in Advance.

I don't think you can use Appian integration objects to "silently" authenticate the user (if that is what you are trying to do). The flow will have be handled by the browser, i.e. the cookies either need to be already present and the target system accepts them, or they are not and the target system will redirect the user to go through some sort of authentication flow.

okay Thank You - I will explore alternatives.