My Oracle Support Banner

OAM 10g: Webgate - Is Setting ObSSOCookie With The httponly Flag on Logout (Doc ID 1279184.1)

Last updated on MAY 09, 2016

Applies to:

COREid Access - Version and later
Information in this document applies to any platform.


The functionality  (ssoCookie:httponly) is enabled by default in Oracle Access Manager 10g ( to ensure that the ObSSOCookie is not accessible to client side scripts such as JavaScript.

To disable this functionality, you specified ssoCookie:disablehttponly in the authentication scheme. This seems to work fine except for the logout scenario, where OAM WebGate is setting ObSSOCookie to "loggedout" with "httponly" property irrespective of setting in the authentication scheme.

Sample header trace for logout:

HTTP/1.1 200 OK
Cache-Control: no-cache
Date: Thu, 30 Dec 2010 18:07:13 GMT
Pragma: no-cache
Content-Length: 1520
Content-Type: text/html
Content-Language: en-US
Last-Modified: Wed, 06 May 2009 16:04:34 GMT
Server: Apache/2.0.52 (Unix)
Set-Cookie: ObSSOCookie=loggedout; httponly; path=/;;
Pragma: no-cache
Expires: -1
Cache-Control: no-cache, no-store


Upgraded to Oracle Access Manager 10g (, and added ssoCookie:disablehttponly in the authentication scheme to disable the httponly flag.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.