Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Login to the WSO2 Identity Server.
  2. In the Configure menu, click User Store Management under Configure.
  3. The default view is as follows, when there are no multiple user stores defined. 

    Info

    You cannot update the 'PRIMARY' user store at run time, so it is not visible in this view.

     

  4. When you click the 'Add Secondary User Store' link, a form is provided to define the user stores.
  5. 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.
    1. ReadWriteLDAPUserStoreManager
    2. ReadOnlyLDAPUserStoreManager
    3. ActiveDirectoryUserStoreManager
    4. 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.
  6. After selecting Once you select the preferred user store manager implementation, it displays a look through and fill the list of properties to that can be filled. It specified. As shown in the following image, it also provides a description of what each property stands for.
  7. Give 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.

  8. Click Add.If  If all the mandatory parameters are filled and a valid domain name is provided, the following notification displays. At this moment, WSO2 Identity Server is attempting to add the new user store to the available chain of user stores.
  9. This is added to the very end of the chain of user stores. 

    Info

    Also note that this message does not imply that user store is added successfully. This can be checked in the following step.

  10. 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.

...