Manage the realm in a federated repository configuration


 

+

Search Tips   |   Advanced Search

 

Overview

The realm can consist of identities in:

Before configuring realms, review...

  1. Federated repositories limitations.

  2. IBM WebSphere Developer Technical Journal: Expand your user registry options with a federated repository


Procedure

  1. Set the realm by using one of the following...

  2. Set supported entity types ...

    Configure supported entity s managing Users and Groups. The Base entry for the default parent determines the repository location where entities of the specified type are placed on a create operation.

  3. Extend the capabilities of storing data and attributes in the realm:

    1. Set an entry mapping repository to store data for managing profiles on multiple repositories.
    2. Set a property extension repository to store attributes that cannot be stored in the LDAP server.
    3. Set up a database repository

  4. To extend the capabilities of LDAP repositories in the realm:

  5. Manage repositories configured in the system

  6. Add an external repository into the realm

  7. Change the password for the repository configured under federated repositories

 

Next steps

  1. After configuring the federated repositories, click Security > Global security to return to the Global security panel. Verify that Federated repositories is identified in the Current realm definition field. If Federated repositories is not identified, select Federated repositories from the Available realm definitions field and click Set as current. To verify the federated repositories configuration, click Apply on the Global security panel. If Federated repositories is not identified in the Current realm definition field, the federated repositories configuration is not used by WAS.

  2. If enabling security, complete the remaining steps as specified in Enable security for the realm. As the final step, validate this setup by clicking Apply in the Global security panel.

  3. Save, stop, and restart all WAS servers (dmgrs, nodes, and Application Servers) for changes in this panel to take effect. If the server comes up without any problems, the setup is correct.


Realm settings
Federated repositories limitations
Change the password for a repository under a federated repositories configuration
Use a single built-in, file-based repository in a new configuration under Federated repositories
Set a single built-in, file-based repository in a new configuration under federated repositories using wsadmin
Change a federated repository configuration to include a single built-in, file-based repository only
Set a single, LDAP repository in a new configuration under Federated repositories
Change a federated repository configuration to include a single, LDAP repository only
Set multiple LDAP repositories in a federated repository configuration
Set a single built-in, file-based repository and one or more LDAP repositories in a federated repository configuration
Manually configuring a LDAP repository in a federated repository configuration
Set LDAP in a federated repository configuration
Add an external repository in a federated repository configuration
Set a property extension repository in a federated repository configuration
Set an entry mapping repository in a federated repository configuration
Set supported entity types in a federated repository configuration
Manage repositories in a federated repository configuration
Increasing the performance of the federated repository configuration
Use custom adapters for federated repositories
Establishing custom adapters for federated repositories
Set custom adapters for federated repositories using wsadmin
Set LDAP entity types in a federated repository configuration
Set group attribute definition settings in a federated repository configuration
Set member attributes in a federated repository configuration
Set dynamic member attributes in a federated repository configuration