Manage the realm in a federated repository configuration
The realm can consist of identities in:
- The file-based repository built into the system
- One or more external repositories
- Both the built-in, file-based repository and in one or more external repositories
Before configuring the realm, review Federated repositories limitations.
Tasks
- Configure the realm using one of the following topics...
- Configure a single, LDAP repository under federated repositories
- Configure multiple LDAP repositories in a federated repository
- Configure a built-in, file-based repository and LDAP repositories in a federated repository
- Add a file-based repository to a federated repositories configuration
- Change a federated repository configuration to include a LDAP repository only
- Change a federated repository configuration to include a single built-in, file-based repository only
- Configure supported entity types
Configure supported entity types before managing 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.
- Configure the mapping for user or group attributes of a user registry to federated repository properties in the realm
- Optional: Under Additional properties, click the Custom properties link to configure custom properties.
- Optional: Use one or more of the following tasks to extend the capabilities of storing data and attributes in the realm:
- Configure an entry mapping repository
An entry mapping repository is used to store data for managing profiles on multiple repositories.
- Configure a property extension repository
A property extension repository is used to store attributes that cannot be stored in the LDAP server.
- Optional: Use one or more of the following advanced user tasks to extend the capabilities of LDAP repositories in the realm:
- Increase the performance of an LDAP repository in a federated repository configuration
- Configure LDAP entity types in a federated repository configuration
- Configure group attribute definition settings in a federated repository configuration
- Optional: Manage configured repositories
- Optional: Add an external repository into the realm
- Optional: Change the password for the repository configured under federated repositories
What to do next
- 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 WebSphere Application Server.
- If we are enabling security, complete the remaining steps as specified in Enable WebSphere Application Server security. As the final step, validate this setup by clicking Apply in the Global security panel.
- 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.
Subtopics
- Federated repositories
- Realm configuration settings
- User attribute mapping for federated repositories
- Custom repository details for federated repositories
- Add federated repository settings
- Federated repositories limitations
- Changing 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
- Add a file-based repository to a federated repositories configuration
- Enable client certificate login support for a file-based repository in federated repositories
- Configure 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
- 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
- Manually configuring an LDAP repository in a federated repository configuration
- Configure LDAP in a federated repository configuration
- Migrate a stand-alone LDAP repository to a federated repositories LDAP 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
- Configure user repository attribute mapping in a federated repository configuration
- Manage repositories in a federated repository configuration
- Increasing the performance of an LDAP repository in a federated repository configuration
- Use custom adapters for federated repositories
- Establish custom adapters for federated repositories
- Add a custom repository to a federated repositories configuration
- Configure custom adapters for federated repositories using wsadmin
- Configure the user registry bridge for federated repositories
- Configure LDAP entity types in a federated repository configuration
- Configure LDAP attributes 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