Integrating Crowd with Spring Security

The content on this page relates to platforms which are not supported for Crowd. Consequently, Atlassian can not guarantee providing any support for the steps described on this page. Please be aware that this material is provided for your information only and that you use it at your own risk.

Crowd provides centralized authentication and single sign-on connectors for the web security framework Spring Security. Spring Security provides a modular and highly configurable approach to authentication and authorization for J2EE applications.

If your web application already makes use of the Spring Security framework for authentication and authorization, you can use the Crowd Spring Security connector to allow your application to easily delegate authentication and authorization requests to Crowd.

Spring, Acegi and Crowd versions

Spring Security was formerly known as Acegi. There is a separate tutorial for integrating Acegi with Crowd. The connector is developed and tested with Spring Security 3.1 from Crowd 2.5 and later. Please use a previous supported release of Crowd if you require compatibility with Spring Security 2.0.4.

Please consult the Spring Security suggested steps or reference guide for a thorough insight into the Spring Security framework. You might also find useful information in our Appfuse integration tutorial.

This guide assumes developer-level knowledge and a Spring Security-based web application

This guide is for developers rather than administrators. This guide assumes you have Crowd 2.5 or later installed and that you want to integrate your Spring Security-based web application with Crowd's security server. The documentation below describes how to integrate Crowd with your own application that uses the Spring Security framework. It assumes you already use Spring Security in your application. If you need help integrating the Spring Security framework with your web application, have look at some of the Spring Security documentation.


  1. Download and configure Crowd. Refer to the Crowd Installation Guide for detailed information on how to do this. We will refer to the Crowd root folder as CROWD.
  2. Have your Spring Security-based custom application ready for tweaking. We will refer to your custom application as 'SpringSecApp'.

Step 1. Configuring Crowd to Talk to your Spring Security Application

Crowd needs to be aware that SpringSecApp will be making authentication requests to Crowd. In brief, you will need to do the following:

  1. Add the SpringSecApp application to Crowd.
  2. Add and configure the directories visible to SpringSecApp.
  3. Add and map the groups which are allowed to authenticate with SpringSecApp.

Please see Adding an Application for a detailed guide.

Step 2. Installing the Crowd Spring Security Connector

2.1 Adding the Crowd Spring Security Connector to your Spring Security Application

You will need to add the Crowd Spring Security connector library and its associated dependencies to your Spring Security application. You can do this manually by copying over the JAR files to your Spring Security application or, if your Spring Security application is a Maven project, you can add the Crowd Spring Security connector as a project dependency. Both methods are described below.

2.1.1 Manually Adding the Crowd Spring Security Connector Libraries

(info) Follow either 2.1.1 or 2.1.2 (not both).

Copy the Crowd integration libraries and configuration files. This is described in the Client Configuration documentation. You will need to copy at least the following file to your Spring Security application:

Copy From

Copy To


(this file is not included in the crowd distribution, you need to download it from




2.1.2 Adding the Crowd Spring Security Connector as a Maven Dependency

(info) Follow either 2.1.1 or 2.1.2 (not both).

Add to your pom.xml:




    <!-- Crowd needs at runtime -->

Ensure you have dependencies on the spring- modules to pick up the versions of Spring required by Crowd rather than the possibly lower version specified by Spring Security.

2.2 Adding the Cache Configuration File

Copy the following file into your application's classpath:

Copy From

Copy To



This file can be tweaked to change the cache behavior.

2.3 Configuring the Crowd Spring Security Connector Properties

The Crowd Spring Security connector needs to be configured with the details of the Crowd server.

  1. Copy the default file to the classpath of your Spring Security application:

    Copy From

    Copy To



  2. Edit and populate the following fields appropriately:


    Same as application name defined when adding the application to Crowd in Step 1.


    Same as application password defined when adding the application to Crowd in Step 1.




    This is the time interval between requests which validate whether the user is logged in or out of the Crowd SSO server. Set to 0, if you want authentication checks to occur on each request. Otherwise set to the number of minutes you wish to wait between requests. Setting this value to 1 or higher will increase the performance of Crowd's integration.

You can read more about the file.

Step 3. Configuring your Spring Security Application to Use the Crowd Spring Security Connector

There are two ways you can integrate your application with Crowd:

  • Centralized user management: The user repository available to your application will be the user repository allocated to your application via Crowd. This means that your application will use the centralized user repository for retrieving user details as well as performing authentication.
  • Single sign-on: In addition to centralized authentication, SSO will be available to your application. If any other SSO-enabled applications (such as JiraConfluence, or your own custom applications) are integrated with Crowd, then SSO behavior will be established across these applications. If you sign in to one application, you are signed in to all applications. If you sign out of one application, you are signed out of all applications.

First, you will need to add the Crowd client application context to wire up the Crowd beans that manage the communication to Crowd. You can do this by including the applicationContext-CrowdRestClient.xml Spring configuration file, found in crowd-integration-client-rest.jar. For example, if you are configuring Spring using a context listener, you can add the following parameter in your your Spring Security application's WEB-INF/web.xml:

3.1 Configuring Centralized User Management

The following sections assume that you have the Spring Security schema mapped to the security namespace. Perform the following updates to your Spring Security configuration:

  1. Add the definition of the CrowdUserDetailsService:

    <bean id="crowdUserDetailsService" class="com.atlassian.crowd.integration.springsecurity.user.CrowdUserDetailsServiceImpl">
            <property name="crowdClient" ref="crowdClient"/>
            <property name="authorityPrefix" value="ROLE_"/>
  2. Add the definition of the RemoteCrowdAuthenticationProvider:

    <bean id="crowdAuthenticationProvider" class="com.atlassian.crowd.integration.springsecurity.RemoteCrowdAuthenticationProvider">
    	<constructor-arg ref="crowdClient"/>
        <constructor-arg ref="crowdHttpAuthenticator"/>
        <constructor-arg ref="crowdUserDetailsService"/>
tip/resting Created with Sketch.

Controlling granted authority names

Rather than taking the group name and setting a prefix, you can define a mapping to grant specific authorities when a user belongs to Crowd groups:

    <util:map id="groupToAuthorityMappings">
        <beans:entry key="crowd-administrators" value="ROLE_crowd-administrators" />
        <beans:entry key="some-other-group" value="specific-authority-for-other-group" />

and then set it on the crowdUserDetailsService:

    <beans:bean id="crowdUserDetailsService" class="com.atlassian.crowd.integration.springsecurity.user.CrowdUserDetailsServiceImpl">
        <beans:property name="groupToAuthorityMappings">
            <beans:bean factory-bean="groupToAuthorityMappings" factory-method="entrySet" />
tip/resting Created with Sketch.

Further extensions

  • If you have an existing user data model, then you can extend or wrap the CrowdDetailsService to cater for user objects within your application domain.
  • If you require users within Crowd to be created in your application's persistence model so that you can store application-specific user data, you can extend the CrowdAuthenticationProvider to create records for successfully authenticated Crowd users.

Crowd's remote API

We recommend that applications do not store the Crowd users locally. Rather, applications should query users via Crowd's remote API.

3.2 Configuring Single Sign-On (SSO)

SSO is optional and requires centralized user management

Single sign-on is optional. If you wish to configure SSO you must first configure centralized user management as described in step 3.1 above.

Perform the following additional updates to your Spring Security configuration:

  1. Remove defaults from the <http/>element:
    1. Remove the auto-config attribute and add an entry-point-ref="crowdAuthenticationProcessingFilterEntryPoint" attribute to the http element.
    2. Remove the <form-login> element.

    3. Include custom-filters for login and logout.
      You should end up with http elements similar to this:

      <http pattern='/styles/*' security='none'/>
      <http pattern='/scripts/*' security='none'/>
      <http auto-config="false"
          <custom-filter position="FORM_LOGIN_FILTER" ref='authenticationProcessingFilter'/>
          <custom-filter position="LOGOUT_FILTER" ref='logoutFilter'/>
          <intercept-url pattern="/admin/*" access="ROLE_application-administrators"/>
          <intercept-url pattern="/passwordHint.html" access="ROLE_ANONYMOUS,ROLE_ADMIN,ROLE_USER"/>
          <intercept-url pattern="/**/*.html*" access="IS_AUTHENTICATED_FULLY"/>
  2. Change the default processing filter to Crowd's SSO filter by adding the following bean definitions:

    <authentication-manager alias="authenticationManager">
        <authentication-provider ref='crowdAuthenticationProvider' />
    <beans:bean id="crowdAuthenticationProcessingFilterEntryPoint" class="">
    	<beans:constructor-arg value="/login.jsp"/>
    <beans:bean id="authenticationProcessingFilter" class="com.atlassian.crowd.integration.springsecurity.CrowdSSOAuthenticationProcessingFilter">
        <beans:constructor-arg ref="tokenHelper"/>
        <beans:constructor-arg ref="crowdClient"/>
        <beans:constructor-arg ref="clientProperties"/>
        <beans:property name="httpAuthenticator" ref="crowdHttpAuthenticator"/>
        <beans:property name="authenticationManager" ref="authenticationManager"/>
        <beans:property name="filterProcessesUrl" value="/j_security_check"/>
        <beans:property name="authenticationFailureHandler">
            <beans:bean class="com.atlassian.crowd.integration.springsecurity.UsernameStoringAuthenticationFailureHandler">
                <beans:property name="defaultFailureUrl" value="/login.jsp?error=true"/>
        <beans:property name="authenticationSuccessHandler">
            <beans:bean class="">
                <beans:property name="defaultTargetUrl" value="/"/>
  3. Add the definition of the CrowdLogoutHandler and add in a LogoutFilter that references it:

    <beans:bean id="crowdLogoutHandler" class="com.atlassian.crowd.integration.springsecurity.CrowdLogoutHandler">
        <beans:property name="httpAuthenticator" ref="crowdHttpAuthenticator"/>
    <beans:bean id="logoutFilter" class="">
        <beans:constructor-arg value="/index.jsp"/>
                <beans:ref bean="crowdLogoutHandler"/>
                <beans:bean class=""/>
        <beans:property name="filterProcessesUrl" value="/logout.jsp"/>

Step 4. Restarting your Spring Security Application

Bounce your application. You should now have centralized authentication and single sign-on with Crowd.


For the purposes of Crowd integration with Spring Security, you should map Spring Security's roles to Crowd's groups. To put it another way: in order to use Spring Security's authorization features, users in Crowd will have their Spring Security roles specified by their group names.

The authorities granted will use the authorityPrefix specified on crowdUserDetailsService. If no suffix is specified, the authorities will append the Crowd group name.

For example if user 'admin' is in the 'crowd-admin' group, then the user 'admin' will be authorized to view pages restricted to the 'ROLE_crowd-admin' role in Spring Security.

    <intercept-url pattern="/console/secure/**" access="ROLE_crowd-administrators"/>
    <intercept-url pattern="/console/info/**" access="ROLE_crowd-users"/>
    <intercept-url pattern="/console/user/**" access="IS_AUTHENTICATED_FULLY"/>

If authoritySuffix is also specified, any user in the mapped groups configured in crowd will be granted "authorityPrefix + authoritySuffix" (for example, ROLE_ADMIN).

<beans:bean id="crowdUserDetailsService" ...>
    <beans:property name="authorityPrefix" value="ROLE_"/>
    <beans:property name="authorityPrefix" value="ADMIN"/>

    <intercept-url pattern="/console/secure/**" access="ROLE_ADMIN"/>
    <intercept-url pattern="/console/user/**" access="IS_AUTHENTICATED_FULLY"/>

Crowd ドキュメント

最終更新日: 2021 年 10 月 6 日


Powered by Confluence and Scroll Viewport.