Bug 56666 - Improve code that clears SSO cookie
Summary: Improve code that clears SSO cookie
Alias: None
Product: Tomcat 8
Classification: Unclassified
Component: Catalina (show other bugs)
Version: 8.0.8
Hardware: PC All
: P2 normal (vote)
Target Milestone: ----
Assignee: Tomcat Developers Mailing List
Depends on:
Reported: 2014-06-24 14:03 UTC by Konstantin Kolinko
Modified: 2014-07-03 11:58 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Konstantin Kolinko 2014-06-24 14:03:26 UTC
Thread on users@: "Regarding JSESSIONIDSSO Cookie maintained by tomcat"

The code for clearing the cookie is in


The code for setting the cookie is in

I see the following issues with the code that clears the cookie in SingleSignOn.invoke():

1). The cookie value is echoed back.
To clear a cookie it should be enough to use any fixed value.

(OP concerns are that Secure and HttpOnly flags are not set on the Set-Cookie header. It should not be an issue, as the value is known to be invalid, and as browser is expected to immediately remove the cookie. Still I can agree that it is not pretty).

2) The Domain and Path attributes should have the same values as for a newly created SSO cookie.

(The new cookie replaces the old cookie if it has the same name, domain and path. - RFC 6265 page 24
- Chapter 5.3. Storage Model, item 11)

BTW, an unrelated issue:
The code in SingleSignOn.invoke() operates on the first SSO cookie that it finds. It does not expect browser to send several cookies with this name.
Comment 1 Mark Thomas 2014-07-03 11:36:11 UTC
Fixed in 8.0.x for 8.0.10 onwards.
Comment 2 Mark Thomas 2014-07-03 11:58:57 UTC
Fixed in 7.0.x for 7.0.55 onwards.