Map attributes - Windows
To map attributes between WebSphere Portal and the user registry:
- Create...
WP_PROFILE/ConfigEngine/log/availableAttributes.html...by running...
cd WP_PROFILE/ConfigEngine
./ConfigEngine.bat wp-query-attribute-config -DWasPassword=passwordThis file lists the available attributes for Users (PersonAccount) and Groups parameters.
- Open the config trace file to review the following output for the PersonAccount and Group entity type:
- The following attributes are defined in WebSphere Portal but not in the LDAP server
This list contains all attributes that are defined in WebSphere Portal but not available in the LDAP. Flag attributes that you do not plan to use in WebSphere Portal as unsupported. Map the attributes that you plan to use to the attributes that exist in the LDAP. Also map...
- uid
- cn
- firstName
- sn
- preferredLanguage
- ibm-primaryEmail attributes.
- The following attributes are flagged as required in the LDAP server but not in WebSphere Portal
This list contains all attributes that are defined as "MUST" in the LDAP server but not as required in WebSphere Portal. You should flag these attributes as required within WebSphere Portal.
- The following attributes have a different type in WebSphere Portal and in the LDAP server
This list contains all attributes that WebSphere Portal might ignore because the data type within WebSphere Portal and within the LDAP server do not match.
- Edit...
WP_PROFILE/ConfigEngine/properties/wkplc.properties- Enter a value for one of the following sets of parameters in wkplc.properties to correct any issues found in the config trace file:
- Save changes to wkplc.properties.
- Run one of the following tasks to update the LDAP user registry configuration with the list of unsupported attributes and the proper mapping between WebSphere Portal and the LDAP user registry:
Option Description Stand-alone cd WP_PROFILE/ConfigEngine
./ConfigEngine.bat wp-update-standalone-ldap-attribute-config -DWasPassword=wpsadminFederated cd WP_PROFILE/ConfigEngine
./ConfigEngine.bat wp-update-federated-ldap-attribute-config -DWasPassword=wpsadmin- To propagate the security changes:
Option Description Stand-alone environment cd WP_PROFILE/bin
./stopServer.sh server1 -username adminid -password passwd
./stopServer.sh WebSphere_Portal -username adminid -password passwd
./startServer.sh server1
./startServer.sh WebSphere_PortalClustered environment cd dmgr_profile_root\bin
./stopManager.sh
cd WP_PROFILE/bin
./stopNode.sh -username adminid -password passwd
./stopServer.sh server1 -username adminid -password passwd
./stopServer.sh WebSphere_Portal -username adminid -password passwd
cd dmgr_profile_root\bin
./startManager.sh
cd WP_PROFILE/bin
./startNode.sh
./startServer.sh server1
./startServer.sh WebSphere_Portal- Optional
To flag an attribute as either unsupported or required for the entire WebSphere Portal environment instead of just for the specified LDAP:
- Enter a value for the following required parameters in wkplc.properties:
- user.attributes.required
- user.attributes.nonsupported
- Save changes to wkplc.properties.
- cd WP_PROFILE/ConfigEngine
./ConfigEngine.bat wp-update-attribute-config -DWasPassword=wpsadmin- Stop and restart the deployment manager, the node agent(s), server1, and the WebSphere_Portal servers.
Parent topic
Manage attributes
Previous topic:
Adding attributes