Updating your user registry on AIX®
After you deploy IBM® WebSphere® Portal, you might need to adjust your stand-alone LDAP user registry or to your federated user repository configurations. You can update these configurations to achieve the user registry configuration.
About this task
- AIX: Adding a database user registry
Add a database user registry to the default federated repository to store user account information for authentication and authorization. You can add multiple database user registries to the default federated repository although you can add only one database user registry at a time. - Configuring a property extension database on AIX
You can configure a property extension database (previously referred to as a lookaside database) to store attributes that the LDAP directory does not or cannot store. Which you want to include in your portal user registry. This situation often occurs when you are using an LDAP directory that does not allow schema extensions for new attributes to support portal applications. When you configure a property extension database, you effectively extend the user registry to make new attributes available as part of your portal user profile. However, it is preferable to store all user attributes in the main user registry. You must complete this task only if you cannot add new attributes to your LDAP directory. The topic explains how to configure property extensions in a single-server environment and in a clustered environment. - Changing from a stand-alone repository to a federated repository on AIX
If you originally configured a stand-alone LDAP user registry but find that you need a more robust security configuration, you can change to the federated user repository. - Updating the base entry on AIX
After you create your base entries, you might need to update the distinguished name (DN) in the repository that uniquely identifies the base entry name. This task applies only to federated repository configurations. This task does not update the base DN entry if you use a stand-alone repository. - Updating the database user registry on AIX
After creating and using the database user registry, you can run the wp-update-db task to update the database user ID, password, and/or the database where the data is stored. This task does not change the DN structure stored in the database repository. - Updating the federated LDAP user registry on AIX
After creating and using the LDAP user registry in the default federated repository, you may find that your LDAP user registry is not working exactly as you would like. You can easily update the LDAP user registry and make the necessary changes. For example, you can change your LDAP Bind password. - Updating the realm configuration on AIX
After you create and use the realms in the default federated repository, you might find that your realm configuration is not working exactly as you would like. You can easily update the realm configurations and make the necessary changes. - Creating the entity type on AIX
If an entity type exists within IBM WebSphere Portal that you want to use but it does not exist within your LDAP user registry, you can create the entity type within your LDAP user registry and then add the relative distinguished name (RDN) to the entity type to map it between WebSphere Portal and your LDAP user registry. - Updating an entity type on AIX
After adding your user registry, you may find that you need to update a single entity type with the value of the default parent. For example, if you delete a repository, you will need to update the entity type if it points to the deleted repository. - Updating a group member on AIX
After you create your LDAP user registry, you might find that your group member is not correct. You can update the group member in your LDAP user registry configuration. - Updating the stand-alone LDAP user registry on AIX
After configuring and using the standalone LDAP user registry, you may find that your LDAP user registry is not working exactly as you would like. You can easily update the LDAP user registry and make the necessary changes. For example, you can change your LDAP Bind password. This task removes any existing attribute mappings. Review all existing attribute mappings before proceeding so you can re-create them after completing this task. - Updating the group membership configuration on AIX
When you configure your LDAP user registry, a group membership is automatically created. You may need to adjust the group membership configuration if you notice high loads on the LDAP server and/or long response times on authentication requests. - Updating the context pool configuration on AIX
After configuring your LDAP user registry, you may find that you need to adjust the number of context instances concurrently maintained by the content pool in order to increase performance.