WSO2 Business Process Server now supports dynamic configuration of multiple user stores. This also allows users to configure their own user stores, out-of-the-box. WSO2 Business Process Server's default configuration has a single user store. If required, it can be configured to connect to multiple user stores as well, so that users in any of the configured user stores are able to login and perform operations depending on their roles/permissions. This section explains how to setup multiple user stores in WSO2 Business Process Server.
To configure multiple user stores:
- Login to the WSO2 Business Process Server.
- In the Configure menu, click User Store Management under Configure.
The default view is as follows, when there are no multiple user stores defined.
You cannot update the 'PRIMARY' user store at run time, so it is not visible in this view.
- When you click the 'Add Secondary User Store' link, a form is provided to define the user stores.
- First select the required implementation of user store manager from the drop-down menu. By default, all the Carbon products come with four user store manager implementations.
- ReadWriteLDAPUserStoreManager
- ReadOnlyLDAPUserStoreManager
- ActiveDirectoryUserStoreManager
- JDBCUserStoreManager
- Additionally, if you want other custom user store manager implementations to be available, it is also possible. A sample custom user store manager can be found in the repository. Once it is added to the server it also appears in this drop-down menu.
- After selecting the preferred user store manager implementation, it displays a list of properties to be filled. It also provides a description of what each property stands for.
Give a unique domain name and fill all the mandatory fields with the values corresponding to the user store.
Domain name should not include the '_' (underscore) character.
- Click Add.
- If all the mandatory parameters are filled and a valid domain name is provided, the following notification displays. At this moment, WSO2 Business Process Server is attempting to add the new user store to the available chain of user stores.
This is added to the very end of the chain of user stores.
Also note that this message does not imply that user store is added successfully. This can be checked in the following step.
- Refresh the page to see the new user store in the table, if it is successfully added.
- Now we have a newly defined secondary (every user store which is not a primary user store is defined as secondary) user store in action. You can also edit the properties of the defined secondary user stores and enable/disable them in a dynamic manner.
It is also possible to just create the user-mgt.xml manually and just drop it to the relevant configuration folder.
- If it is configuration of a super tenant, the secondary user store definitions should go to '
CARBON_HOME/repository/deployment/server/userstores'. - If it is a general tenant, the configuration should go to '
CARBON_HOME/repository/tenants/<tenantid>/userstores'. - Also the file name needs to be in accordance with the domain name to avoid conflicts (e.g.: if domain name is wso2.com, the file name of the configuration file should be wso2_com.xml).
- One file only contains the definition for one user store domain.
- If it is configuration of a super tenant, the secondary user store definitions should go to '