Browser Cache Issue

[Former Member]

Hi Everybody,

We are using SAP Netweaver 7.3 Portal and integrated ABAP webdynpro applications by creating iviews in portal. SSO is configured and working fine.

Issue:-

Browser cache memory is not clearing  when we log off the respective user from the portal –  due to this applications behaves as same user even we log in with different user. If we manually clear the Browser cache, we are able to see the second user's application.

Any suggestions on how to resolve this issue will be really helpful.

Thanks,

Krishnaveni.

[Former Member · Accepted solution]

Hi Krishnaveni,

This sounds similar to this problem: http://scn.sap.com/message/13401467#13401467 I wonder if this is a known issue or emerging known issue? What exact portal version are you using including SP level? Are you using AJAX framework? If you logoff do you also close the browser window or just re-login in the same window?

Thanks,
Simon

[Former Member · Accepted solution]

Hi,

Thanks for your immediate response.

Our portal version is 7.3 with SP level 7.0. Yes, we are using AJAX framework concept. 

Post log off from the first user we tried with both the options:  By closing the browser window or re-login in the same window.  In both the cases it’s not working. Until unless we are not clearing the browser cache manually it will not work.

Thanks,

Krishnaveni.

[Former Member]

Hi Krishnaveni,

I am also facing the same issue.Can you please clarify how you have resolved this issue,It will be very helpful for us.

Our portal version is 7.30 sp 9,IE browser IE8.

Thanks in advance.

Regards,

Nibedita

[Former Member]

Hi Nibedita,

Please go through the following SAP Note:

1717945 - Portal Logoff Does Not Logoff the Backend When Using HTTP Security Session Management

This should fix the issue.

BR,

Anurag

[Former Member]

Hi Anurag,

Thanks for your reply.My issue has resolved after applying the sap note.Thank you.

Regards,

Nibedita

[Former Member]

Hi Nibedita,

Glad that it worked!!!

BR,

Anurag

[Steve_S1]

Great find here..  This note worked for us as well..

We upgraded our ECC 6.0 to EhP6 and this issue showed itself on our NW 7.0 Portal.

We applied this note, and all is well now..

Thanks,

Steve

[Former Member]

Hi

Do you see the same behavior while using IE and other browsers. What is the version of IE your on.

Thanks

Kiran Nekkanti

[Former Member]

Our corporate browser is IE8, but I also noticed the same behavior with chrome.

We are running EP7.31 and just upgraded our back-end system from 7.01 to 7.31.

We kept our 7.01 system as back-up. Our Portal is linked to the new and old back-end systems.

The user switching works fine when we go to 7.01 but fails with 7.31.

Any idea what to check? Maybe there's a SSO misconfiguration somewhere?

[Former Member]

for SSO Can you check the jco rfc of the backed system. Click on connection test and see if the response is good.

Use full qualified domain name and Dont use Administrator ID. use your own id.

also clear all caches from Portal.

Also check alias name for backed system in system configuration

[Noel_Hendrikx]

Tip:

If you start a new browser session, session cache will not be available.

Check out:

http://downloadsquad.switched.com/2009/05/08/ie8s-new-session-feature-allows-multiple-logins-to-web-...

For testing purpose, the -nomerge option is great!

[Former Member]

Yes in a new session, the issue does not exist anymore. But that's not satisfying for our end users.

[Noel_Hendrikx]

Your problem sounds familiar. In the browsers memory the ticket to the backend is still available after logoff, right?

After logging off from the portal, you will need to login to the java stack (portal). This will work with a different user. But when you go to a webdynpro abap application, the old user information is displayed (meaning a privacy risk!).

The only thing I can think of is closing the browser before logging in again. There is no function in javascript to clear the browser cache unfortunately.

In another reply I read something about two different backend systems. It is strange that the problem does not occur on the old system, meaning this isn't a browser issue...

Sounds like a SSO misconfiguration indeed.

[Former Member]

Hi Noel,

Yes, you get it, it's exactly what's happening.

I've double checked the connection to the back-end, recreated a new one and it still appears. When I configure the connection to our old system it works well. Is there something to check in the back ends ?

[Former Member]

Hi Krishnaveni,

We are experiencing a similar issue. Were you able to solve your problem? How did you do it?

Thanks,

Nicolas

[SandipAgarwalla]

Krishan

What is the cache property set for the ABAP web dynpro application in the Portal PCD? What is the value?

Normally you can cache iviews in the client side (browser), but it normally should not show same content for diff users specially if the Content is dynamic...

If its static content (like HTML), then its retrieved from the browser cache..

Thanks

Sandip

[Former Member]

Hi Sandip,

Thanks for your valuable input.

Below are the Cache related Property and its value in the Portal PCD which is set for ABAP WD application.

Cache Level = None

Cache Validity Period = -1

Thanks,

Krishnaveni.

[Former Member]

Hi Krishnaveni,

Have you tried to access the ABAP Webdynpro app directly (e.g. not via the portal)? Is it the portal that is caching (e.g. the Portal Menu) or is it the Web Dynpro App that is being cached?

Thanks,
Simon

[Former Member]

Hi Simon,

Thanks for your reply.

Masthead is changing correctly for different logged in users and the roles are appearing correctly. When we click on the wd application iview it is taking to the previous user's content. If i clear the browser cache, it will give the correct content.

Thanks,

Krishnaveni.

[SandipAgarwalla]

Have you enabled any of these on the Server

1) PCD Cache

2) Portal runtime cache

3) Navigation CACHE (though this should not affect)

Try clearing the PCD Cache from the server once, it may help (not sure, but wild guess)

Else raise a Ticket with SAP..

Thanks

Sandip

[hofmann]

By SSO you mean SSO between the portal and WD ABAP, and not between the browser and the portal. So the user has to log on to the portal by providing the credentials, right?

The 2nd user has to do the log on to the portal or is already logged on when he access the portal: the logoff from 1st user really worked?

By cleaning the cache you mean: deleting the cached files or also deleting the cookies? Have you checked the SSO cookies? Are they for the 1st or 2nd user?

The WDA app of the 2nd user differs from the 1st one or do you see the 1st user name still in the masthead?