Crowd Integration Fails due to Internal Server Error
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptom
After integrating Crowd with JIRA, reports the error: An internal server error occurred when requesting resource
The following error is logged in atlassian-jira.log file,
010-10-19 10:07:41,971 http-8080-1 ERROR [500ErrorPage.jsp] Exception caught in 500 page com/atlassian/seraph/auth/LoginReason
java.lang.NoClassDefFoundError: com/atlassian/seraph/auth/LoginReason
at com.atlassian.crowd.integration.seraph.v22.CrowdAuthenticator.login(CrowdAuthenticator.java:86)
at com.atlassian.seraph.filter.PasswordBasedLoginFilter.runAuthentication(PasswordBasedLoginFilter.java:121)
Cause
The issue is caused due to invalid seraph-config.xml configuration.
Resolution
Find the following line:
<authenticator class="com.atlassian.crowd.integration.seraph.v22.JIRAAuthenticator"/>
and change it to:
<authenticator class="com.atlassian.crowd.integration.seraph.JIRAAuthenticator"/>