The authentication in the Apache Rave portal is handled through Spring Security. The supported login mechanisms are currently basic authentication with users stored in the database, OpenId and, since version 0.8-incubating, LDAP.

When an LDAP user logs in for the first time in the Apache Rave portal, a user profile in the portal is created with the same username, email address and display name as in the LDAP. When this user logs in again, he is still authenticated against the LDAP server.

Demo login

For the LDAP authentication the demo setup comes with an embedded ApacheDS. To login with the demo setup the following credentials can be used:

  • johnldap/johnldap
  • janeldap/janeldap

LDAP configuration

The demo setup of the Apache Rave portal is configured to use an embedded ApacheDS, populated by a users.ldiff file:

<security:ldap-server ldif="classpath:users.ldiff" root="dc=rave,dc=apache,dc=org" />

Authentication is handled by LDAP first. If this fails, Spring Security tries the basic authentication against the database:


        <security:password-encoder ref="passwordEncoder"/>

An Apache Rave portal specific class maps the authenticated LDAP user to an Apache Rave portal profile:

<bean id="raveUserContextMapper" class="" >
    <constructor-arg name="userService" ref="userService"/>
    <constructor-arg name="newAccountService" ref="defaultNewAccountService"/>
    <constructor-arg name="mailAttributeName" value="mail"/>
    <constructor-arg name="displayNameAttributeName" value="displayName"/>
    <constructor-arg name="pageLayoutCode" value="columns_3"/>

With "mailAttributeName" and "displayNameAttributeName" you can configure the names of the attributes from your own LDAP that contain the mail address and display name for a user. When the LdapUserDetailsContextMapper create a user profile, the user gets access to the portal and gets the layout configured in "pageLayoutCode".

Customizing the LDAP setup

First create a custom portal project. There are multiple ways to build your custom Apache Rave instance, but the quickest is to use a Maven WAR overlay. See Extending Rave for an example overlay.

For the LDAP configuration, the default applicationContext-security.xml needs to be overridden.

LDAP as only authentication provider

If you don't want the fallback to the database for authentication, remove:

<security:authentication-provider user-service-ref="userService">
     <security:password-encoder ref="passwordEncoder"/>

External LDAP server

The following line is configured to use the embedded ApacheDS:

<security:ldap-server ldif="classpath:users.ldiff" root="dc=rave,dc=apache,dc=org" />

To use an external LDAP server, replace it with:

<ldap-server id="appLdapServer"
        manager-dn="uid=admin,ou=system" manager-password="secret" />