SSO not working for a custom WDA application that runs in the Portal

[Former Member]

I have a Portal system (Java stack, NW04s) that has an iView of type webDynpro ABAP. The custom Web Dynpro ABAP application resides on another system (ABAP stack, running ECC6). We have configured the trust relationship between the Portal and the ECC system as per

http://help.sap.com/saphelp_nw04s/helpdata/en/61/42897de269cf44b35f9395978cc9cb/content.htm

We know this is working since we are able to run ESS. However, for the custom WebDynpro ABAP application, when calling it for the first time, a logon screen shows up. How can we get rid of it? what are we missing to have SSO work for the custom WebDynpro application?

[Former Member]

Please check this link:

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d35bb690-0201-0010-988a-d669c853...

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.highlightedcontent?documenturi=...

Hope it helps.

Regards,

Mona

[josef_pfandl]

We have the same problem - did you find any solution?

We guess, it has to do something with different instances of ABAP. Even when directly (without EP) logging on to the WDA, the error appears, when changing the URL in the browser to an instance running on a different server (it does not happen, when using a different instance running on the same server - we use AIX and SSO works perfectly in all other configurations). It seems as the browser (the session-cookie) looses info about client and language, as, if the user also exists in the default-client of ABAP, it seems to work.

Ideas, anybody?