Soulwing CAS Client version 0.6.0
Release Notes
25 February 2011

Release 0.6.0 addresses the following issue:
[SCC-91] - Tomcat plugin: Custom <Context> to override <login-config> in web.xml 

Release 0.5.3 addresses the following issues:
[SCC-29] - Soulwing Confluence Client logout broken when used with AdaptaVist 
ThemeBuilder 
[SCC-44] - Confluence plugin: join groups on log in
[SCC-47] - Tomcat plugin: using principal caching with session
[SCC-49] - Tomcat plugin: LogoutValve improvement
[SCC-56] - Allow names for XML elements/attributes in CAS protocol to be 
configurable

Release 0.5.2a fixes the following issue:
[SCC-54] - UrlFactoryGenerator is appending extra path info to full 
(correct) URI

Release 0.5.2 fixes the following issues:

[SCC-45] - CAS server returns a HTTP status of 500 for stale ticket.  Now the
client redirects to the CAS login URL in this case, resulting in a better 
end-user experience
[SCC-46] - Must create session before sending redirect in CasAuthenticator
used by Tomcat plugin
[SCC-53] - UrlGeneratorFactory must check for empty pathInfo string 

Release 0.5.1 fixes the following issues:

[SCC-28] - Using the client with JIRA no longer causes an exception related to
HTTP session creation.  Thanks to Jens Wilke for the patch.
[SCC-38] - Extra path information used by JIRA and Confluence is now correctly included
in the CAS service URL.
[SCC-40] - When using a post validation redirect path, an extra slash (/) 
character is no longer included in the URL sent to the browser.

Release 0.4.3 fixes the following issue:

[SCC-38] - Extra path information used by JIRA and Confluence is now correctly included
in the CAS service URL