Skip to Content
0
Former Member
Mar 27, 2008 at 06:49 PM

Portal session not being terminated

24 Views

When we upgraded from EP 6.0 to NW 2004, users started recieving the

Netweaver Login Screen when they logged out and logged back in, in the

same browser. We think this error occurs because NW 2004 implements Web

Services Remote Portal functionality.

We are using SiteMinder as a third party session management tool.

What we found was that the Siteminder session was being killed but the

Portal session was not. Therefore, when users logged back in they would

see the generic Netweaver Login Screen, and they could actually just

hit "enter" and continue to the portal.

A successful logoff, users clicked the logoff button, the DSM terminator

was being called, thus killing the portal session, then a form was

submitted redirecting the users the the siteminder loggoff page, which

logs the users off siteminder.

When the logoff failed, we found that after the DSM Terminator was called

and before the page was being redirected, a portal component

(WSRPSessionRelease) was being called, which in turn, recreated the

portal session. So the user never actually gets logged off from the

portal.

We found that the WSRPSessionRelease component is set to

a "browser" "unload" event when the portallauncher.default component is

first loaded. This is the same component that is being called when the

user clicks the "X" to force close the browser.

Not everytime is the WSRPSessionRelase component being called before the

redirect to the siteminder logg off page. Sometimes this component is

called after the redirect, and we find that this is a successful loggoff.

The component is:

irj/servlet/prt/portal/prtroot/com.sap.portal.wsrp.coreconsumer.WSRPSessio

nRelease