Fiori Launchpad cookie sap-usercontext

[mark_taylor3]

Hi

I have a Fiori Launchpad configured that has Fiori applications as well as tiles for Web Dynpro Abap and direct url based applications. My problem comes about because the WDA applications are on a different server /client to the Front end server so once I have launched a tile that points at the WDA using system aliases, it starts the application fine but sets the sap-usercontext cookie which contains the new sap-client number. Unfortunately, after launching WDA tile any subsequent calls to Fiori tiles or their dynamic data results in an authentication prompt as the sap-usercontext still points at the old WDA client which is not valid for these frontend applications. How can I avoid this behaviour?

Thanks

Mark

[k3ivi]

We had the same problem with 2 sessions. One was from system client 010 and another 410.

0002530317 did not fully resolved that issue. This change will give you another unwanted problem when you run more clients on the same system resulting in every call ending in client you specified.

We have implemented this webdispatcher rule on our 010 system. It removes problematic cookie part sap-client=410 from http header.

if "%{HTTP_COOKIE}" regimatch "sap-usercontext=sap-language=EN&sap-client=410" [OR]

if "%{HTTP_COOKIE}" regimatch "sap-usercontext=sap-language=DE&sap-client=410"

RemoveCookie "sap-usercontext

or If this does not work just simple command:

RemoveCookie "sap-usercontext"

[Former Member]

Hi Mark and JP,

Please check note 0002530317

[JurijsP]

Hi,

Have you solved the issue? I'm facing same issue now.

Thanks!

JP