The default User Store
The primary user store that is configured by default in the user-mgt.xml file is a JDBC user store, which reads/writes into the internal database of the product server. By default, the internal database is H2 for all WSO2 products excluding the Identity Server. 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-only LDAP/AD as the primary user store:
Step 1: Setting up the read-only LDAP/AD user store manager
Before you begin
- If you create the
user-mgt.xmlfile yourself, be sure to save it in the
classattribute for a read-only LDAP/Active Directory is
Uncomment the following user store in the
<UserStoreManager class="org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager">. Also, ensure that you comment out the configurations for any other user stores in the same file.
Given below is a sample for the LDAP/AD user store configuration in read-only mode. You can change the values to match your LDAP/AD. For descriptions of the user store properties, see the related documentation.
Update the connection details to match your user store. For example:
For Active Directory, the connectionURL should have the following format:
If you are using
ldaps(secured) to connect to the Active Directory as shown below, you need to import the certificate of Active Directory to the
client-truststore.jksof the WSO2 product. See the topic on configuring keystores for information on how to add certificates to the trust-store.
Obtain a user who has permission to read all users/attributes and perform searches on the user store from your LDAP/Active Directory administrator. For example, if the privileged user is AdminLDAP and the password is 2010#Avrudu, update the following sections of the user store configuration as shown below. Note that this user does NOT have to be the system administrator that you define here.
<Property name="UserSearchBase">with the directory name where the users are stored. When LDAP searches for users, it will start from this location of the directory.
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/Active Directory administrator.
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 users, it will start from this location of the directory. For example:
Set the GroupSearchFilter and GroupNameAttributes. For example:
MembershipAttributeproperty as shown below:
To read roles based on a backlink attribute, use the following code snipet instead of the above:
For Active Directory, you can use
<Property name="Referral">follow</Property>to enable referrals within the user store. The AD user store may be partitioned into multiple domains. However, according to the use store configurations in the
user-mgt.xmlfile, we are only connecting to one of the domains. Therefore, when a request for an object is received to the user store, the
<Property name="Referral">follow</Property>property ensures that all the domains in the directory will be searched to locate the requested object.
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. The
<Configuration> section in the
user-mgt.xml file contains the super admin information. Update this configuration for the read-only LDAP/AD as explained below.
- <AddAdmin>: This should be set to 'False' as it will not be allowed to create users and roles in a read-only user store.
- <AdminRole>: The admin role you enter here should already exist in the read-only user store. Otherwise, you must enter an internal role, which will be saved to the internal database of the system when the system starts the first time.
- <AdminUser>: Since we are configuring a read-only LDAP as the primary user store, 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. For example, say a valid username is AdminSOA. Update the
<AdminUser>section of your configuration as shown above. You do not have to update the password element as it is already set in the user store.
See the related documentation for more information about the system administrator.
Step 3: Starting the server
Start your server and try to log in as the admin user you specified. The password is the admin user's password in the LDAP server.