Mode d’authentification

By default the catalog uses the internal database for user management and authentication. However there are some other authentication mechanisms available:

Configuration du LDAP

To enable LDAP, setup authentication by including WEB-INF/config-security/config-security-ldap.xml in WEB-INF/config-security/config-security.xml, uncommenting the following line:

<import resource="config-security-ldap.xml"/>

The LDAP configuration is defined in WEB-INF/config-security/, you can then configure your environment updating the previous file or overriding the properties in the file WEB-INF/config-security/

  1. Define the LDAP connection:

    • ldap.base.provider.url: This tells the portal where the LDAP server is located. Make sure that the computer with the catalog can hit the computer with the LDAP server. Check to make sure that the appropriate ports are opened, etc.

    • ldap.base.dn: this will usually look something like: “dc=organizationnamehere,dc=org”

    • & Define LDAP administrator user to use to bind to LDAP. If not define, an anonymous bind is made. Principal is the username and credentials property the password.

    # LDAP security properties

    To verify that you have the correct settings, try to connect to the LDAP server using an LDAP browser application.

  2. Define where to find users in LDAP structure for authentication:

    • this is where the catalog will look for users for authentication.

    • ldap.base.dn.pattern: this is the distinguished name for the user to bind with. {0} is replaced by the user name typed in the sign in screen.

Authorization Settings

When using LDAP, the user information and privileges for GeoNetwork could be defined from the LDAP attributes.

User information

The user information could be retrieved from the LDAP configuring for each user attribute in the catalog database which LDAP attributes match. If the attribute is empty or not defined, a default value could be defined. The property value is composed by two parts separated by , character. The first part is the attribute name and the second part is the default value in case the attribute name is not define or the attribute value in LDAP is empty.

The configuration is the following:

# Map user information to LDAP attributes and default values
# ldapUserContextMapper.mapping[name]=ldap_attribute,default_value

Privileges configuration

User groups and user profiles could be set optionally from LDAP information or not. By default user privileges are managed from the local database. If LDAP information should be used to define user privileges, set the ldap.privilege.import property true:


When importing privileges from LDAP, the catalog administrator could decide to create groups defined in the LDAP and not defined in local database. For this set the following property to true:


In order to define which groups the user is member of and which profile is the user:

# If not set, the default profile is RegisteredUser
# Valid profiles are

Attributes configuration:

  • privilege attribute contains the group this user is member of. More than one group is allowed.

  • profile attribute contains the profile of the user.

User valid profiles are:

  • Administrator

  • UserAdmin

  • Reviewer

  • Editor

  • RegisteredUser

  • Guest

If LDAP attribute containing profiles does not match the catalog profile list, a mapping could be defined:

# Map LDAP custom profiles to catalog profiles. Not used if ldap.privilege.pattern is defined.

For example, in the previous configuration, the attribute value Admin will be mapped to Administrator (which is a valid profile for the catalog).

An attribute could define both the profile and the group for a user. To extract this information, a custom pattern could be defined to populate user privileges according to that attribute:

  1. Define one attribute for the profile and one for groups in WEB-INF/config-security/

# In
  1. Define one attribute for the privilege and define a custom pattern:

# In

Enable the bean ldapUserContextMapper for LDAPUserDetailsContextMapperWithPattern` in WEB-INF/config-security/config-security-ldap.xml).

  <!--<bean id="ldapUserContextMapper"
      <property name="mapping">
      <property name="profileMapping">
      <property name="ldapBaseDn" value="${ldap.base.dn}"/>
      <property name="importPrivilegesFromLdap" value="${ldap.privilege.import}"/>
      <property name="createNonExistingLdapGroup"
      <property name="createNonExistingLdapUser" value="${ldap.privilege.create.nonexisting.users}"/>
      <property name="ldapManager" ref="ldapUserDetailsService"/>
      <property name="contextSource" ref="contextSource"/>
      <property name="ldapUsernameCaseInsensitive" value="${ldap.usernameCaseInsensitive:#{true}}"/>

  <bean id="ldapUserContextMapper" class="">
    <property name="mapping">
    <property name="profileMapping">
    <property name="importPrivilegesFromLdap" value="${ldap.privilege.import}"/>
    <property name="createNonExistingLdapGroup" value="${ldap.privilege.create.nonexisting.groups}" />
    <property name="createNonExistingLdapUser" value="${ldap.privilege.create.nonexisting.users}" />

    <property name="ldapManager" ref="ldapUserDetailsService" />

    <property name="privilegePattern" value="${ldap.privilege.pattern}" />
    <property name="groupIndexInPattern" value="${}"/>
    <property name="profilIndexInPattern" value="${ldap.privilege.pattern.idx.profil}"/>

    <property name="contextSource" ref="contextSource" />
  1. Define custom location for extracting group and role (no support for group/role combination) (use LDAPUserDetailsContextMapperWithProfileSearch in config-security.xml).*)(memberUid=uid={0},${},${ldap.base.dn})(cn=EL_*))*)(memberUid=uid={0},${},${ldap.base.dn})(|(cn=SP_*)(cn=EL_*)))*)*)(memberUid=uid={0},${},${ldap.base.dn})(cn=SV_*))*)

The LDAP attribute can contains the following configuration to define the different type of users, for example:


-- Define a reviewer for the group GRANULAT

-- Define a reviewer for the group GRANULAT and editor for MIMEL

-- Define a reviewer for the group GRANULAT and editor for MIMEL and RegisteredUser for NATURA2000

-- Only a registered user for GRANULAT


A synchronization task is taking care of removing LDAP user which may be deleted. For example:

  • T0: a user A sign in the catalog. A local user A is created in the user database

  • T1: A is deleted from the LDAP (A could not sign in in the catalog anymore)

  • T2: the synchronization task will check that all local LDAP users exist in LDAP:

    • if user is not owner of any records, it will be deleted

    • if user is owner of metadata records, warning message is avaialable on the catalog logging system. record’s owner should be changed to another user before the task could remove the user.

By default the task is runned once every day. Configuration could be changed in the following property:

# Run LDAP sync every day at 23:30
ldap.sync.cron=0 30 23 * * ?

The following properties allow advanced configuration of the synchronisation process:${}*)(mail=*@*)(givenName=*))*))*)


If connection fails, try to increase logging for LDAP in WEB-INF/classes/log4j.xml:

<logger name="geonetwork.ldap" additivity="false">
    <level value="DEBUG"/>

Or from the Configuration Settings set the Log level to DEV temporary:


Configuration du CAS

To enable CAS, setup authentication by including WEB-INF/config-security/config-security-cas.xml in WEB-INF/config-security/config-security.xml, uncommenting the following lines:

<import resource="config-security-cas.xml"/>
<import resource="config-security-cas-ldap.xml"/>

CAS can use either ldap or a database for user management, to use a database uncomment the following lines instead:

<import resource="config-security-cas.xml"/>
<import resource="config-security-cas-database.xml"/>

The CAS configuration is defined in WEB-INF/config-security/, you can then configure your environment updating the previous file or overriding the properties in the file WEB-INF/config-security/


Configuration de Shibboleth

The catalog can operate in a SAML secured federation. Shibboleth should be installed in apache as described here. The catalog is accessed via apache. Setup shibboleth authentication by including WEB-INF/config-security/config-security-shibboleth.xml in WEB-INF/config-security/config-security.xml. You can then configure your environment in