OBIEE 11g: After Configuring OHS Caching, OBIEE Login User Can Not Be Switched. The Last Login Information Unexpectedly Saved in The Browser's Cache.
Last updated on OCTOBER 05, 2017
Applies to:Business Intelligence Suite Enterprise Edition - Version 184.108.40.206.0 to 220.127.116.11.170718 [Release 11g]
Information in this document applies to any platform.
We build an Oracle Http Server(OHS) in front of OBIEE. And add configuration directives for handling static files in biinternal_vh.conf file.
- Regarding biinternal_vh.conf file,please refer to
7.5.2 Creating .conf Files to Define <VirtualHost> Directives
- Regarding expiry of static files,please refer to
To add configuration directives for handling static files
"7.10.2 Configuring Oracle HTTP Server for Static File Caching"
Configuration for Oracle HTTP Server is similar to configuration for Apache HTTP Server
According to the above documentation, OHS can also set the expiration date of static files.
However, after configuring the above setting, OBIEE login users can not be switched. The last login information unexpectedly saved in the browser's cache.
1. Access OBIEE with User A via OHS.
2. Open any catalog.
3. Sign out OBIEE.
4. Re-sign in as a different User B.
5. Access the catalog.
The catalog opened is not appropriate; logged in User B has turned the User A who last logged in.
In sawlog.log, you see the following error:
[2017-09-26T17:40:46.000+09:00] [OBIPS] [ERROR:31] 
00iiAbeBk3x5AhUpM49Die0001Ng00008D,0:1:1] [tid: 4452] Invalid request. Note
that some urls may not be bookmarked or emailed.[[
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms