Add more attributes to VMM

After installing IBM WebSphere Portal, and configuring the LDAP user registries, adapt the attribute configuration to match business needs. Do not complete these steps if we configured only a database user registry or the default federated file-based repository for out-of-box installations.

Portal has a predefined set of attributes for users and groups. Your LDAP server might have a different set of predefined user and group attributes. We can configure extra attributes. Flag the attributes as required or unsupported on a per repository basis or for all repositories.

LDAP servers can handle only attributes explicitly defined in their schema. The LDAP schema is different from the WebSphere Portal schema. The two schemas are required to match for communication between WebSphere Portal and the LDAP server. The task to add the LDAP user registry does some basic attribute configurations, but we may still have to adapt the portal configuration to match the LDAP schema. If an attribute is in WebSphere Portal, but not in the LDAP server, complete one of the following tasks to resolve this mismatch:

• Flag the attribute as unsupported for the LDAP server
• Introduce an attribute mapping that maps the WebSphere Portal attribute to an attribute defined in the LDAP schema

Use the following tasks to adapt the attribute configuration to match business needs.

• Query the defined attributes
• Add attributes
• Mapping attributes
• Remove attributes

Parent User registry

Related tasks:
People Finder attribute mapping
People Finder