-
Bug
-
Resolution: Fixed
-
High
-
3.4
-
WAR/EAR distribution, Sun Java 1.6.0_21, Tomcat 6, Debian/GNU Linux (squeezy)
Original Description
After upgrading Confluence from 3.3.3 to 3.4 I'm receiving the following exception.
I checked all the crowd configuration, it's all in the required place, including the crowd-integration jar-file...
javax.servlet.ServletException: Filter execution threw an exception
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:259)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.atlassian.security.auth.trustedapps.filter.TrustedApplicationsFilter.doFilter(TrustedApplicationsFilter.java:98)
at com.atlassian.confluence.util.AbstractBootstrapHotSwappingFilter.doFilter(AbstractBootstrapHotSwappingFilter.java:30)
...
Caused by: java.lang.NoSuchMethodError: com.atlassian.crowd.integration.seraph.CrowdAuthenticator.getLoginCookieKey()Ljava/lang/String;
at com.atlassian.crowd.integration.seraph.CrowdAuthenticator.autoLoginToCrowd(CrowdAuthenticator.java:225)
at com.atlassian.crowd.integration.seraph.CrowdAuthenticator.isAuthenticated(CrowdAuthenticator.java:166)
at com.atlassian.crowd.integration.seraph.CrowdAuthenticator.getUser(CrowdAuthenticator.java:280)
at com.atlassian.seraph.filter.SecurityFilter.doFilter(SecurityFilter.java:129)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
... 67 more
Resolution
Refer to our KB Article
- relates to
-
-
- Closed
-
[CONFSERVER-21046] Upgrade to Confluence 3.4 throws NoSuchMethodError when using Crowd SSO
Dear Christian,
Although unrelated to the bug you have reported, I notice you are using Java 1.6.0_21.
Please be aware of http://jira.atlassian.com/browse/CONF-19049 where users have reported that Update 18 and above can cause the JVM to crash.
Kind Regards,
Partha Kamal
Hi Christian,
Sorry we didn't make it clear that confluence 3.4 need to upgrade to crowd 2.0.7
When integrating with Crowd Confluence 3.4 requires a new version of the crowd library: 2.0.7. When upgrading to the new version of crowd you will also need to change
{CONFLUENCE/confluence/WEB-INF/seraph-config.xml}file; authenticator needs to be changed to:
<authenticator class="com.atlassian.crowd.integration.seraph.v22.ConfluenceAuthenticator"/>
We are updating the upgrade docs and crowd docs to reflect that. Thanks for pointing it out.
Anatoli.
[Update]
I can confirm the workaround made in this post http://forums.atlassian.com/thread.jspa?messageID=257356266
After succesfully logging in using a different atlassian application I can now user Confluence 3.4 without any problems...
There seems to be a problem logging into confluence 3.4 using the crowd integration, while simple verifiing the existing user-session is working fine :-/
The documentation has been updated to the correct instructions.