Need to send cookie to non-SAP backend from URL iView

Question

Hi,
I have a backend application which takes a cookie for
(non-SAP) SSO purposes. I have created an URL iView
in my EP 6.0 SP2 that correctly displays the content
of that web page, i. e. the login screen.
However, even when I have a cookie in my browser, it still
displays that login screen, i. e. the cookie is either
not sent or not recognized.
I then created a simple test servlet on a backend server
that prints the contents of all the HTTP headers. When
I connect my browser directly to that page, I can see
the cookie. When I connect my iView to that URL, I
do not see the cookie. So apparently the iView does
not send the cookie.
As I learned, in EP 6.0 SP3 there is a "Fetch Mode"
property for URL iViews which allow to define whether
the URL in the URL iView should be retrieved by the
server or the client. This seems to indicate that in
SP2, always the server issues that request, which would
explain why there is no cookie in the request (since only
the browser holds these cookies). So I presume if I
would use SP3 with Fetch-Mode set to Client, this might
work. But then again, this fetch mode is not really
encouraged by the documentation and only recommended
if you are really desparate ...
So the question basically is:
- are my assumptions above correct?
- is there a way to have the EP server send cookies to
  my backend systems with SP2?
I'm a little puzzled that this doesn't work out of the
box, since my understanding was that SAP SSO tokens are
also transported to backend systems using cookies, and
this is supposed to be on by default for EP. So I was
expecting to see at least the SAP SSO tokens in all
HTTP requests to backends. Apparently, the world is
not that easy.
Any insights would very much appreciated!
Thanks,
Matthias

Answer 1

Additional thoughts:
In general your assumptions are correct. When using client side fetch mode then the cookie should be forwarded, and I would not expect problems there. When using server side mode then the cookie domain changes and becomes the portal domain, and as a result the cookie is kept in the browser, but is a little useless. I'm not 100% familiar with how we solve this problem when using SSO2 cookie in server side. Yoav, can you elaborate ?
     The reason the documentation was not in favor of client side is because at the time the idea was to encourage the users to use the portal server cache. However, this seems less relevant now, because only the first request will be cached, but not the inner calls of the html page.
     Bottom line - I don't see any issue with using client side, and actually the default in FP is client side. So I would simply modify the iview to use it.