Problem auto logoff SAP Portal with WD ABAP events

[brunoambrozio]

Hi guys,

I have followed the excellent tutorial described on the follow link to set a custom auto logoff on SAP Portal when is detected an user idlleness.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/309379b6-bb9b-2d10-feb1-91f2a7078...

It has worked perfectly in most of situations, but in one specific it is taking in a trouble.

We have set up a timeout for user idlleness as 10 minutes. If the user logs into the SAP Portal, stay idlle for 5 minutes and start navigating on WD ABAP applications, theorically the idlle time should be restarted to 0, but it isn´t. After 5 minutes, even the user browsing on the applications,  the auto logoff is executed and the user is redirected to logon page, because the 10 minutes are reached

It seems WD ABAP events don´t notify the client about the actions executed on it so javascript can´t handle this situation.

Can someone help me?

Thanks.

Bruno

[Former Member · Accepted solution]

I guess your analysis is correct. Unless the WDA triggers a navigation request through the Portal API, portal won't get notified. WDAs are getting accessed from the backend system directly by the client.

Unless you want to implement some kind of fancy warning popup before the timeout is reached, there is no need for custom timeout functionality. Both AS JAVA and AS ABAP have timeout handling.

[brunoambrozio · Accepted solution]

Hello Samuli,

Configuring the same timeout to everybody would be nice, but this isn´t our real scenario.

The customer has terminals where users in the factory access their personal information and for this scenario, they would like to set a different timeout.

Until now, the solution was perfect, I had created a system url alias for this terminals, created the timeout portal application and associated to a custom portal framework. The other areas would access by other url alias without this timeout application, using session ticket to control the timeout.

But when we started testing, this situation came up. I have already opened an OSS to SAP and they confirmed that there is no standard solution for this.

Do you have another idea? Any workaound?

Thanks.

Bruno

[Former Member · Accepted solution]

You could add a second iView hosting a custom Java component on the portal page hosting the WDA. Then in the method WDDOMODIFY of the WDA you would send a portal event which you would capture in the custom Java component and reset the timer accordingly. Make sure portal eventing between the iViews on the portal page work. See this link on how to trigger a portal event from the WDA.

[brunoambrozio · Accepted solution]

This would be a good idea, if the WD4A applications weren´t standard. These are ESS/MSS applications, so it´s impractible to do it.

I will discuss with IT team to find an operational system solution.

I let you know when I have the results.

Thanks mate.

[Former Member · Accepted solution]

Use the enhancement framework. You can implement Post-Exit methods for the WDDOMODIFY method of the standard ESS/MSS applications involved.