Page Comparison

WSO2 Storage Server's default configuration The default configuration of WSO2 products has a single user store. If required, it can be configured you can configure WSO2 products to connect to multiple several secondary user stores as well. After configuration, so that users in any of the configured user stores are able to login from different stores can log in and perform operations depending on their roles/permissions. This section explains how to set up multiple user stores in WSO2 Storage Server.

To configure multiple user stores via the UI:

...

The default view is as follows, when there are no multiple user stores defined. 

...

You can also configure your own customized user stores and connect them with the products as secondary stores.

The topics below show how to configure secondary user stores manually or using the management console: 

Configuring using the management console

1. Log in to the management console and click User Store Management sub menu under Configure menu.

2. The User Store Management page opens. Initially, there are no secondary user stores.

   Info
   Note: You cannot update the PRIMARY user store at run time, so it is not visible in on this viewpage.

   Image Removed

    

3. Click Add Secondary User Store.

The following form appears, where you can define a secondary user store:.
Image RemovedFirst

5. The User Store Manager page opens. Enter a unique domain name and fill in the rest of the data.

   Info
   Do not include underscore character (_) in domain names.

   For details on each property, see the respective property description that is provided. Also, select the required implementation of user store manager from

the drop-down menu

6. the User Store Manager Class drop-down list. The displayed property list varies depending on the selected user store manager implementation. By default, all

the Carbon

7. WSO2 products come with four user store manager implementations

.

8. as follows:

   • ReadWriteLDAPUserStoreManager
   • ReadOnlyLDAPUserStoreManager
   • ActiveDirectoryUserStoreManager
   • JDBCUserStoreManager

   You can also

add

9. populate this drop-down 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.

Once it is added to the server it also appears in this drop-down menu.
10. Once you select the preferred user store manager implementation, look through and fill the list of properties that can be specified. As shown in the following image, it also provides a description of each property.

11. Provide a unique domain name and fill all the mandatory fields with the values corresponding to the user store. 

    Info
    Domain name should not include the '_' (underscore) character.

12. Click Add. A notification appears indicating that the user store is in the process of being added to the end of the chain of user stores.
    Image Removed

13. Refresh the page to see the new user store in the table, if it is successfully added.
    Image Removed

...

1. Image Added

    

2. Ensure that all the mandatory fields are filled and a valid domain name is given and click Add. 

3. A message appears saying that the user stores are being added. 
   Image Added

   Info
   Note: The above message does not imply that the user store is added successfully. It simply means that the server is attempting to add the new user store to the end of the available chain of stores.

4. Refresh the page after a few seconds to check the status. 

5. If the new user store is successfully added, it will appear in the User Store Management page.

6. After adding to the server, you can edit the properties of the new secondary user store and enable/disable it in a dynamic manner.

Configuring

...

manually

...

By default, the configuration of the primary user store is saved in the user-mgt.xml file. When  When you create a secondary user store, its configuration is saved to an XML file with the same name as the domain you specified. If desiredrequired, you can create this XML file manually and save it as follows:

• • If it is configuration of a super tenant, save the secondary user store definitions
should go to '<CARBON
• • in <PRODUCT_HOME>/repository/deployment/server/
userstores'
• • userstores directory.
  • If it is a general tenant, save the configuration
should go to '<CARBON
• • in <PRODUCT_HOME>/repository/tenants/<tenantid>/
userstores'
• • userstores directory.
  • The
file should
• • secondary user store configuration file must have the same name as the domain with an underscore (_) in place of the period. For example, if the domain
is 
• • is wso2.com,
name
• •  name the file
as follows:
• • as  wso2_com.xml.
  • One file only contains the definition for one user store domain.