By default, WSO2 products have a single, embedded user store. If required, you can configure WSO2 products to connect to multiple secondary user stores as well. After configuration, users from different stores can log in and perform operations depending on their roles/permissions. You can als o configure your own customized user stores and connect them with the products as secondary stores.
The topics below explain how to configure secondary user stores manually or using the management console:
| Table of Contents |
|---|
| Tip |
|---|
Tip: If you set up a database other than the default H2 that comes with the product to store user information, select the script relevant to your database type from the |
Configuring using the management console
...
| Info |
|---|
Note: You cannot update the PRIMARY user store at run time, so it is not visible on this page. |
...
Click Add Secondary User Store.
...
In the User Store Manager Class list, select the type of user store you are creating:
| User store manager | Description |
|---|---|
org.wso2.carbon.user.core.ldap.ReadOnlyLDAPUserStoreManager | Use |
org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager | Use |
org.wso2.carbon.user.core.ldap.ActiveDirectoryUserStoreManager | Use |
org.wso2.carbon.user.core.jdbc.JDBCUserStoreManager | Use |
You can also populate this list with custom user store manager implementations by adding them to the server. A sample custom user store manager can be found in the repository.
...
Enter a unique domain name with no underscore (_) characters, and optionally enter a description for this user store.
...
Enter values for the properties, using the descriptions in the Descriptions column for guidance. The properties that appear vary based on the user store manager class you selected, and there may be additional properties in an Optional or Advanced section at the bottom of the screen.
...
Ensure that all the mandatory fields are filled in and click Add.
...
A message appears indicating that the server is updating the user stores. At this point, the server is attempting to add the new user store to the end of the available chain of stores.
...
Refresh the page after a few seconds to verify that the user store was added successfully and now appears in the list of secondary user stores.
You can now edit the properties of the new secondary user store and enable/disable it as needed.
Configuring manually
By default, the configuration of the primary user store is saved in the < file. When you create a secondary user store using the management console as explained above, its configuration is saved to an XML file with the same name as the domain name you specify. Alternatively, you can create this XML file manually and save it using the following guidelines:PRODUCT_HOME>/repository/conf/user-mgt.xml
...
| Include Page | ||||
|---|---|---|---|---|
|
- Properties of User Stores: This topic explains the properties that are used when defining user stores.