Portal, V6.1

---

 

Update your user registry on Solaris

After deploying IBM WebSphere Portal, you may need to make adjustments to your standalone LDAP user registry or to your federated user repository configurations. You can update these configurations to achieve the proper user registry configuration.

Perform the following tasks to update your user registry configurations:

• Adding a database user registry on Solaris
  Add a database user registry to the default federated repository to store user account information for authorization.

• Configure a property extension database on Solaris
  Configure IBM WebSphere Portal to use a property extension to store additional attributes that cannot be stored in the LDAP user registry.

• Modifying to the federated repository on Solaris
  If you originally configured a standalone 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 Solaris
  After creating your base entries, you may find that you need to update the distinguished name in the repository that uniquely identifies the base entry name.

• Updating the database user registry on Solaris
  After creating and using the database user registry, you can run the wp-update-db 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 Solaris
  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 update the LDAP user registry and make the necessary changes. For example, you can change your LDAP Bind password.

• Updating the realm configuration on Solaris
  After creating and using the realms in the default federated repository, you may 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 Solaris
  After creating your LDAP user registry, you may find that your LDAP user registry requires additional entity types. You can create new entity types in your LDAP user registry configuration.

• Updating an entity type on Solaris
  After adding your user registry, you may find that 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.

• Adding the RDN to the entity type on Solaris
  After creating your LDAP user registry, you may find that your entity type is not correct or you created a new entity type to your LDAP user registry. You can add a relative distinguished name (RDN) to an existing entity type in your LDAP user registry configuration.

• Updating a group member on Solaris
  After creating your LDAP user registry, you may 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 Solaris
  After configuring and using the stand-alone 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.

• Updating the group membership configuration on Solaris
  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 Solaris
  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.

 

Parent topic

Configure security on Solaris

---