Answered

Passing Cookies Between HTTP Actions

(0) Share

Report

Posted on by timrodman

Is there a way to pass cookies between HTTP actions in Microsoft Flow?

The first HTTP action is used to authenticate. It gives me back a cookie. Then I need to pass that cookie to a second HTTP action.

I was able to get this to work in PHP with a cookie jar (click here), but I can't get it to work in Microsoft Flow.

Note: It was actually working by passing headers a couple of weeks ago, but now it doesn't work anymore. I have a separate thread already on that issue (click here), but I thought I would start a new thread since I couldn't find any threads specifically talking about passing cookies between HTTP actions. I hope it's ok that I started a new thread.

Categories:

General topics

I have the same question (0)

All responses (17)

Answers (2)

v-xida-msft on at

Like (1)

Report

Hi @timrodman,

Could you please share a screenshot of your flow's configuration?
I afraid that there is no way to pass cookies between HTTP Actions in Microsoft Flow currently, if you would like this featured to be added soon, please submit an idea to Flow Ideas Forum:

https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas

Best regards,

Kris

Was this reply helpful? Yes No
timrodman 21 on at

Like (1)

Report
Here is a screenshot of the configuration (except that isn't the real password):

And here are the screenshots of what happens when it runs

And the full text of the Headers Outputs / Inputs.

HTTP Headers Outputs

X-Handled-By Acumatica-PX.Export/AuthenticationManagerModule Set-Cookie ASP.NET_SessionId=d5lgfpq2vjyoxsov11cqv43n; path=/; HttpOnly,UserBranch=16; path=/,Locale=Culture=en-US&TimeZone=GMTM0800A; expires=Sun, 19-Nov-2017 14:27:14 GMT; path=/,CompanyID=SalesDemo; expires=Sun, 19-Nov-2017 14:27:14 GMT; path=/,.ASPXAUTH=C2D84F2334AAF6C3DBEAD498F1B13B13E80D7A63172C7572C022A6F65A381884CD04872F20A959F8914FC739673D1BC6CE2A135AEEDC54B50CAF6222D0C98EFD344948D1947CFD6F9674CEE72D16951ED648F8AEF7C4F49485612844005FBD971A6BF10342FB427CCF6CFC48CE332576CCB6441C8B4CDB055576906E16F215B6830D8992; path=/; HttpOnly Server Microsoft-IIS/7.5 X-Powered-By ASP.NET Date Thu, 16 Nov 2017 14:27:14 GMT Content-Length 0
HTTP 2 Headers Inputs
{ "X-Handled-By": "Acumatica-PX.Export/AuthenticationManagerModule", "Set-Cookie": "ASP.NET_SessionId=d5lgfpq2vjyoxsov11cqv43n; path=/; HttpOnly,UserBranch=16; path=/,Locale=Culture=en-US&TimeZone=GMTM0800A; expires=Sun, 19-Nov-2017 14:27:14 GMT; path=/,CompanyID=SalesDemo; expires=Sun, 19-Nov-2017 14:27:14 GMT; path=/,.ASPXAUTH=C2D84F2334AAF6C3DBEAD498F1B13B13E80D7A63172C7572C022A6F65A381884CD04872F20A959F8914FC739673D1BC6CE2A135AEEDC54B50CAF6222D0C98EFD344948D1947CFD6F9674CEE72D16951ED648F8AEF7C4F49485612844005FBD971A6BF10342FB427CCF6CFC48CE332576CCB6441C8B4CDB055576906E16F215B6830D8992; path=/; HttpOnly", "Server": "Microsoft-IIS/7.5", "X-Powered-By": "ASP.NET", "Date": "Thu, 16 Nov 2017 14:27:14 GMT", "Content-Length": "0" }
HTTP 2 Headers Outputs
X-Handled-By Acumatica-PX.Export/AuthenticationManagerModule Set-Cookie ASP.NET_SessionId=b5ztummf1yzvspjuairsbhro; path=/; HttpOnly,Locale=TimeZone=GMTE0000U&Culture=en-US; path=/,UserBranch=; path=/ Server Microsoft-IIS/7.5 X-Powered-By ASP.NET Date Thu, 16 Nov 2017 14:27:14 GMT Content-Length 36 Content-Type application/json; charset=utf-8

Someone pointed out in this thread that it seems funny that the ASP.NET_SessionId in the HTTP 2 Headers Outputs is not the same as the ASP.NET_SessionId in the HTTP 2 Headers Inputs.

Thanks for the suggestion to create an idea for this. I did so (click here).

Was this reply helpful? Yes No
MrThompson 24 on at

Like (1)

Report

I'm having the same issue connecting to a Dell/Quest KACE appliance. It uses a token that is handed back in the Headers, the token is compared to a cookie. With no cookie in flow, can't use Flow with KACE.

"During user authentication, a token is returned in a response header named x-dell-csrf-token. That value must be gathered by the client and sent in a similarly named request header for every subsequent request. This value is compared against a token stored in a client’s cookie. This is a common technique that helps prevent cross-site request forgery (CSRF) attacks."

Was this reply helpful? Yes No
MrThompson 24 on at

Like (0)

Report

Anyone from Microsoft looking to solve this?

Was this reply helpful? Yes No
anhthuch4ng on at

Like (0)

Report

@v-xida-msft - any suggestions on how we can approach this issue?

Thanks!

-AT

Was this reply helpful? Yes No
MrThompson 24 on at

Like (1)

Report

I spoke with MS support, they said they're aware of it and currently no fix or resolution is being offered.

Was this reply helpful? Yes No
samol518 2 on at

Like (0)

Report

Has there been any update on this issue?

Was this reply helpful? Yes No
timrodman 21 on at

Like (0)

Report

Not that I've seen.

Was this reply helpful? Yes No
nguyen51 2 on at

Like (0)

Report

Have you found a work around for this? I'm having similar issues

Was this reply helpful? Yes No
ilkovm 2 on at

Like (0)

Report

Can at least the brains at Microsoft provide a workaround?

Was this reply helpful? Yes No