User management functionality is provided by default in all WSO2 Carbon-based products and is configured in the
user-mgt.xml file found in the
<WSO2_OB_APIM_HOME>/repository/conf/ directories. This file is shipped with user store manager configurations for all possible user store types (JDBC, read-only LDAP/Active Directory, read-write LDAP and read-write Active directory). The instructions given below explains how to configure a read-write LDAP as the primary user store for the WSO2 server.
The default User Store
The primary user store that is configured by default in the user-mgt.xml file of WSO2 products is a JDBC user store, which reads/writes into the internal database of the product server. By default, the internal database is H2. This database is used by the Authorization Manager (for user authentication information) as well as the User Store Manager (for defining users and roles). In the case of the WSO2 Identity Server, the default user store is an LDAP (Apache DS) that is shipped with the product.
Note that the RDBMS used in the default configuration can remain as the database used for storing Authorization information.
Follow the given steps to configure a read-write LDAP as the primary user store:
Step 1: Setting up the read-write LDAP user store manager
Before you begin
- If you create the
user-mgt.xmlfile yourself, be sure to save it in the
<WSO2_OB_KM_HOME>/repository/conf/ and <WSO2_OB_APIM_HOME>/repository/conf/ directories.
classattribute for a read-write LDAP is
Once the above points are made note of and completed, you can start configuring your external read-write LDAP as the primary user store.
<ReadWriteLDAPUserStoreManager>user store manager class in the
user-mgt.xmlfile by uncommenting the relevant code. When it is enabled, the user manager reads/writes into the LDAP user store.
Note that these configurations already exist in the
user-mgt.xmlfile so you only need to uncomment them and make the appropriate adjustments.Also ensure that you comment out the configurations for other user stores that you are not using; in short, you can only configure one primary user store.
The default configuration for the external read/write user store in the
user-mgt.xmlfile is as follows. You may have to change some of these values according to your requirements. For more information about each of the properties used in the
user-mgt.xmlfile for configuring the primary user store, see Properties of User Stores.
To read and write to an LDAPuserstore, it is important to ensure that the
WriteGroupsproperties in the
<WSO2_OB_APIM_HOME>/repository/conf/user-mgt.xmlfiles are set to
Set the attribute to use as the username, typically either
uidfor LDAP. Ideally,
<Property name="UserNameSearchFilter">should refer to the same attribute. If you are not sure what attribute is available in your user store, check with your LDAP administrator.
Specify the following properties that are relevant to connecting to the LDAP in order to perform various tasks.
If you are using
ldaps(secured LDAP) to connect to the LDAP:
You need set the
ConnectionURLas shown below.
You also need to enable connection pooling for LDAPS connections at the time of starting your server, which will enhance server performance.
In WSO2 products based on Carbon 4.4.x, you can set the
LDAPConnectionTimeoutproperty: If the connection to the LDAP is inactive for the length of time (in milliseconds) specified by this property, the connection will be terminated.
ReadGroupsproperty to 'true', if it should be allowed to read roles from this user store. When this property is 'true', you must also specify values for the
GroupNameAttributeproperties. If the
ReadGroupsproperty is set to 'false', only Users can be read from the user store. You can set the configuration to read roles from the user store by reading the user/role mapping based on a membership (user list) or backlink attribute as shown below.
To read the user/role mapping based on a membership (This is used by the
GroupSearchBaseproperty to the directory name where the Roles are stored. That is, the roles you create using the management console of your product will be stored in this directory location. Also, when LDAP searches for groups, it will start from this location of the directory. For example:
Set the GroupSearchFilter andGroupNameAttributes. For example:
MembershipAttributeproperty as shown below:
To read roles based on a backlink attribute, use thefollowingcodesnipetinsteadofthe above:
Step 2: Updating the system administrator
The admin user is the super tenant that will be able to manage all other users, roles and permissions in the system by using the management console of the product. Therefore, the user that should have admin permissions is required to be stored in the user store when you start the system for the first time. Since the LDAP user store can be written to, you have the option of creating a new admin user in the user store when you start the system for the first time. Alternatively, you can also use a user ID that already exists in the LDAP. For information about the system administrator user, see Configuring the System Administrator.
These two alternative configurations can be done as explained below.
If the user store is read-only, find a valid user that already resides in the user store. For example, say a valid username is AdminSOA. Update the
<AdminUser>section of your configuration as shown below. You do not have to update the password element as it is already set in the user store.
If the user store can be written to, you can add the super tenant user to the user store. Therefore,
<AddAdmin>should be set to true as shown below.
Step 3: Starting the server
Start your server and try to log in as the admin user you specified in Step 2.