Set federated repositories

We can define additional repositories as required for the out-of-box federated repositories user registry.

For example, we can define one or more databases and/or LDAP directories for the user registry. Federated repositories also let you implement multiple realms. Realms define subsets of users and are spread across multiple repositories.

For example, we can define one realm in a file-based repository and another realm in an LDAP directory. Because WebSphere Application Server provides an implementation of the UserRegistry interface for federated repositories out-of-box, you do not need to create a custom implementation of this interface.

• Create federated repositories
  Add the custom repository to the default federated repositories. You must implement a custom registry adaptor so that WebSphere Portal can access the repository. After you implement the custom registry adaptor, define several parameters for the environment and run a task to add the repository to the federated repositories.
• Update federated repositories
  We can update the environment parameters we defined when created the federated repository. You should run the task to update the custom repository if you any environment settings have changed such as the base DN. We can also run the update task to change any settings you specified when created the repository.

  For example, run the update task to change support for paging, sorting, and transactions.

Parent: Set up custom user repositories