Loading (cached) resources from restricted URL

Some time ago we have migrated a portlet application from IBM Portal 7 to HCL DX 9.5. We've recently discovered a strange behavior when loading certain page resources.

Here's a scenario:

There are two user groups, group1 and group2, and two users, user1 (that belongs to group1) and user2 (that belongs to group2). User1 has access to page1 and page2, while user2 only has access to page2.

First, user1 logs in and opens page1 (URL similar to http://wp95.mydomain.com/wps/myportal/myapp/page1), then a logout follows and then user2 logs in and access page2 (URL similar to http://wp95.mydomain.com/wps/myportal/myapp/page2). Now this page looks corrupted (missing icons, HTML elements are incorrectly positioned,...) and when we check browser's developer tools, it looks like that an attempt is made to load resources with URL starting with http://wp95.mydomain.com/wps/myportal/myapp/page1. User2 has no access to page1, so we assume that some caching is happening here but we're unable to eliminate that behavior. An important thing to add here - after portlet application is restarted and when user2 tries to open page2, it is displayed correctly and there are no attempts to access URLs starting with http://wp95.mydomain.com/wps/myportal/myapp/page1.

We've tried different page/portlet settings following this article, but no luck.

Can someone explain why this behavior occurs? How can we prevent loading resources from URLs that user has no access to?

Thanks in advance,

Peter

Sounds like an issue best addressed by a support ticket as we will need some har logs to see what is sent.

I would suggest to check that the cookies are cleaned between user1 logged out and user2 logging in - maybe a JSessionID or LTPA token cookie are left behind due to an issue with cookie domains or similar.

How do you test the scenario for these two users? Do you use one and the same web-browser to test this? Do you also see the behavior, when you use different web-browser for testing both users access?

Please keep in mind that the Web-Browsers in general having issues, if you try to connect to one and the same server-URL using a new user, because in such situations sessions are cached on web-browser side for which then unexpected behaviors might coming up. If you just want to test with one web-browser, then I would suggest you to clear all caches and cookies first as soon as you logging out with the first user, before you then try to login with another user. And at best use the incognito mode for the login-tests.

If you still face an issue, then please open a case with HCL support as already suggested by Thomas.