Error when trying to parse first name last name from DN

[brianbolt]

The default user context mapper for LDAP in ldap-authentication-provider does not give direct access to the CN of the user. Instead we rely on putting the CN into the DN of the user. This makes ACAS difficult to work with on many LDAP setups. This change allows the admin to configure the applicationContext-security.xml file to map users using inetOrgPerson which gives direct access to the CN when the object class of the person is inetOrgPerson.

This fix still relies on parsing the CN to get a first and last name but it avoids having to configure LDAP to put the CN into the DN of the user.

To configure this, the admin would:

Add the inetOrgPersonContextMapper bean into their context security file:

  <beans:bean id="postSuccessAuthHandler"
    class="com.labsynch.labseer.service.PostSuccessfulAuthenticationHandler">
  </beans:bean>

  <beans:bean id="inetOrgPersonContextMapper" class="org.springframework.security.ldap.userdetails.InetOrgPersonContextMapper">
  </beans:bean>

And add the user-context-mapper-ref with value inetOrgPersonContextMapper to their ldap-authentication-provider details:

    <ldap-authentication-provider server-ref="ldapServer"
      user-dn-pattern=""
      user-search-filter="uid={0}"
      group-search-filter="(|(member={0})(cn={0}))"
      user-search-base="{{ user_search_base }}"
      group-search-base="{{ group_search_base }}"
      user-context-mapper-ref="inetOrgPersonContextMapper"
      />