Manage the realm in a federated repository configuration

 

+

Search Tips   |   Advanced Search

 

Follow this topic to manage the realm in a federated repository configuration.

The realm can consist of identities in:

Before you configure your realm, review...

 

Procedure

  1. Configure your realm...

  2. Configure supported entity types using the steps

    You must configure supported entity types before you can manage this account with 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. Optional: Use one or more of the following tasks to extend the capabilities of storing data and attributes in your realm:

    1. Configure an entry mapping repository

      An entry mapping repository is used to store data for managing profiles on multiple repositories.

    2. Configure a property extension repository

      A property extension repository is used to store attributes that cannot be stored in your LDAP server.

    1. Set up a database repository using wsadmin commands

     

  4. Optional: Use one or more of the following advanced user tasks to extend the capabilities of LDAP repositories in your realm:

  5. Manage repositories

  6. Optional: Add an external repository into your realm

  7. Optional: Change the password for the repository that is configured under federated repositories

 

What to do next

  1. After configuring the federated repositories, click Security > Secure administration, applications, and infrastructure to return to the Secure administration, applications, and infrastructure 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 Secure administration, applications, and infrastructure panel. If Federated repositories is not identified in the Current realm definition field, your federated repositories configuration is not used by WAS.

  2. If you are enabling security, complete the remaining steps as specified in Enabling security for the realm. As the final step, validate this setup by clicking Apply in the Secure administration, applications, and infrastructure panel.

  3. Save, stop, and restart all the product servers (deployment managers, 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 configuration settings
Limitations of federated repositories
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
Change a federated repository configuration to include a single built-in, file-based repository only
Configure a single, LDAP repository in a new configuration under Federated repositories
Change a federated repository configuration to include a single, LDAP repository only
Configure multiple LDAP repositories in a federated repository configuration
Configure a single built-in, file-based repository and one or more LDAP repositories in a federated repository configuration
Configure LDAP in a federated repository configuration
Add an external repository in a federated repository configuration
Configure a property extension repository in a federated repository configuration
Configure an entry mapping repository in a federated repository configuration
Configure supported entity types in a federated repository configuration
Manage repositories in a federated repository configuration
Increase the performance of the federated repository configuration
Configure LDAP entity types in a federated repository configuration
Configure group attribute definition settings in a federated repository configuration
Configure member attributes in a federated repository configuration
Configure dynamic member attributes in a federated repository configuration