This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit https://wso2.com/documentation/.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Carbon Remote User Store Manager is a way of using a user store that is already configured in a WSO2 Carbon product. 

Consider a scenario where two instances of the WSO2 Identity Server are configured. The first instance (IS1) has a ReadOnlyLDAPUserStoreManager (configured on OpenLDAP) and the second instance (IS2) has JDBCUserStoreManager configured on OracleDB. To expose the users in IS2 to IS1 through the UserStoreManager API, you can call the UserStoreManager admin service operations. WSO2 IS has a standard implementation which uses the admin services. The diagram below illustrates this scenario. 

Configuring a carbon remote user store manager 

To configure a carbon remote user store manager, you can follow the following steps. 

  1. Make sure that the Admin Service WSDLs are exposed in IS2 (the remote server). To do this, set the HideAdminServiceWSDLs property to true in the [CARBON_HOME]/repository/conf/carbon.xml file as shown below.

    <HideAdminServiceWSDLs>true</HideAdminServiceWSDLs>
  2. Log in to the management console of the the local server (IS1) and click User Stores>Add in the Main menu. 
  3. Fill in the following values in the form as seen below. The image below shows a sample configuration.
    • User Store Manager Class:  org.wso2.carbon.identity.user.store.remote.CarbonRemoteUserstoreManger 
    • Domain Name: <desired_secondary_userstore_name>
    • Remote Server Username: <remote_admin_login>
    • Remote Server Password: <remote_admin_password>

    • Remote Server URL(s): https://<remote_sever_url>:<remote_server_port>/services
       

      Make sure that you insert the same credentials used to invoke the admin services in the remote server and the same remote services URL. 


  4. Update other fields as required and click Add. You can use the same steps listed above to configure the remote user store as your secondary user store using admin services. 
  • No labels