+

Search Tips   |   Advanced Search

Portal, V6.1

 

Manage attributes

After installation, IBM WebSphere Portal has a predefined set of attributes for users and groups. Your LDAP server may have a different set of predefined user and group attributes. To ensure proper communication between WebSphere Portal and your LDAP server, you can configure additional attributes and flag existing attributes as required or unsupported on a per repository basis or for all configure repositories. LDAP servers can only handle attributes that are explicitly defined in their schema. The LDAP server's schema is different from the WebSphere Portal schema but the two schemas should match for proper communication between WebSphere Portal and the LDAP server. The task to add the LDAP user registry does some basic attribute configurations depending on the type of LDAP server that you choose. You may, however, still need to adopt the WebSphere Portal configuration to match the LDAP schema. For example...

if an attribute is defined in WebSphere Portal but not in the LDAP server, you will need to perform one of the following tasks to resolve this mismatch

 

Query the defined attributes

You can run the wp-query-attribute-config task any time during the configuration process or at runtime to query an overview of the currently defined attributes. This task creates the availableAttributes.html report, in WP_PROFILE/ConfigEngine/log. The report contains one table that lists the available attributes for Users (PersonAccount) and one table that lists the available attributes for Groups. For each configured repository there is a column that indicates if the attribute is flagged as unsupported or if the attribute is mapped to a different LDAP attribute.

This task does not validate the existence of attributes in the LDAP schema.

 

Update the LDAP server attribute configuration

Run the wp-update-federated-ldap-attribute-config or wp-update-standalone-ldap-attribute-config to flag an attribute as unsupported or to introduce a mapping for the attribute. If you use the wp-update-federated-ldap-attribute-config only one LDAP server is updated, which means that the Selfcare portlet will still offer an attribute that is configured as unsupported for one or more LDAP servers.

 

Update the general attribute configuration

Run the wp-update-attribute-config to flag an attribute as required or unsupported for WebSphere Portal, which means that the Selfcare portlet will indicate that an attribute is required and not list the unsupported ones. You will need to run the wp-update-federated-ldap-attribute-config or wp-update-standalone-ldap-attribute-config task to flag an attribute as required or unsupported in the LDAP server.

 

Parent topic

Manage attributes

Next topic:

Adding attributes