Summary: | Domain for single sign-on cookie | ||
---|---|---|---|
Product: | Tomcat 5 | Reporter: | Oliver Rossmueller <oros> |
Component: | Catalina | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | ||
Priority: | P2 | ||
Version: | 5.5.9 | ||
Target Milestone: | --- | ||
Hardware: | Other | ||
OS: | other | ||
Attachments: |
SSO cookie domain patch
AuthenticatorBase.java patch SingleSignOn.java patch mbeans-descriptors.xml patch |
Description
Oliver Rossmueller
2005-05-03 13:39:17 UTC
Created attachment 14918 [details]
SSO cookie domain patch
It's a good use case, but it's not the right way to do it. You should add an optional attribute on the SSO valve instead. Created attachment 14971 [details]
AuthenticatorBase.java patch
Created attachment 14972 [details]
SingleSignOn.java patch
Created attachment 14973 [details]
mbeans-descriptors.xml patch
I aggree that an optional attribute on the SingleSingOn valve is the more elegant way to specify a domain name for the sso cookie. I modified the implementation in the suggested way (see the three new patches attachted) so the cookie domain can be set on the valve like <Valve className="org.apache.catalina.authenticator.SingleSignOn" cookieDomain=".mydomain.xa"/> I've committed the patch into HEAD, it'll be in 5.5.13. Thank you for contributing it! |