Steps to performed for mapping attributes between WebSphere Portal and your LDAP server:-
* Run below tasks and verify the attributes available in Ldap.
* Open the config trace file to view what properties are being set:
* Enter a value for one of the following sets of parameters in the wkplc.properties file to correct any issues found in the config trace file:
* 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:
* Run below tasks and verify the attributes available in Ldap.
- Stand alone: ConfigEngine.sh wp-validate-standalone-ldap-attribute-config
- Federated: ConfigEngine.sh wp-validate-federated-ldap-attribute-config
* Open the config trace file to view what properties are being set:
- In the trace file you can see how all mappings are taking place from ldap to portal.
- There must be a mapping for uid, cn, firstName, sn, preferredLanguage, and ibm-primaryEmail attributes if they are contained in the list.
- See the step below about flagging an attribute as either unsupported or required.
* Enter a value for one of the following sets of parameters in the wkplc.properties file to correct any issues found in the config trace file:
- standalone.ldap.id
- standalone.ldap.attributes.nonSupported
- standalone.ldap.attributes.nonSupported.delete
- standalone.ldap.attributes.mapping.ldapName
- standalone.ldap.attributes.mapping.portalName
- standalone.ldap.attributes.mapping.entityTypes
* 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:
- Standalone :ConfigEngine.sh wp-update-standalone-ldap-attribute-config
- Federated: ConfigEngine.sh wp-update-federated-ldap-attribute-config
No comments:
Post a Comment