Last updated on APRIL 21, 2011
Applies to:Oracle Containers for J2EE - Version: 184.108.40.206.0 to 10.1.2.1.0 - Release: AS10g to AS10gR2
Information in this document applies to any platform.
Checked for relevancy on 21-April-2011
You are running web applications using the Oracle Containers for J2EE (OC4J) component of Oracle Application Server 9.0.4.x or 10.1.2.x and have these applications and other applications (such as Oracle Portal) secured using Oracle Single Sign On (SSO).
When you invoke the SSO "global logout" mechanism, you are successfully logged out from other applications such as Portal and a user seeking to access portal pages requiring security is immediately asked to re-authenticate via single sign on. However, after "global logout" users are still able to access secured pages for your custom web applications without being redirected to the SSO login page.
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