APAR status
Closed as program error.
Error description
The fix will make it possible to change all LDAP attributes using wp-update-standalone-ldap, except LDAP ID, LDAP host name and base DN, without changing the realm name. In order to change those three attributes, the realm name must still be changed. Observed exception when running ConfigEngine wp-update-standalone-ldap in order to update the LDAP bindPassword: [wplc-delete-federated-ldap-entitytype] id="..." Delete LDAP entity type - result: [com.ibm.websphere.wim.exception.WIMConfigurationException: CWWIM5014E LDAP entity type PersonAccount is not found.] [wplc-delete-federated-ldap-entitytype] com.ibm.websphere.wim.exception.WIMConfigurationException: CWWIM5014E LDAP entity type PersonAccount is not found If the realm name was not changed before calling wp-update-standalone-ldap, following messages can be found in ConfigTrace.log [wplc-create-realm] Realm <name> already exists in the WIM Repository System. Continuing with next task. and [wplc-cleanup-repositories] Repository <repID> not deleted because a base entry exists in the default realm. and [wplc-create-federated-ldap-repository] Repository <repID> already exists in the WIM Repository System. Continuing with next task. As a result, some LDAP attributes will not be changed after calling wp-update-standalone-ldap.
Local fix
NA
Problem summary
The fix will make it possible to change all LDAP attributes using wp-update-standalone-ldap, except LDAP ID, LDAP host name and base DN, without changing the realm name. In order to change those three attributes, the realm name must still be changed. Observed exception when running ConfigEngine wp-update-standalone-ldap in order to update the LDAP bindPassword: [wplc-delete-federated-ldap-entitytype] id="..." Delete LDAP entity type - result: [com.ibm.websphere.wim.exception.WIMConfigurationException: CWWIM5014E LDAP entity type PersonAccount is not found.] [wplc-delete-federated-ldap-entitytype] com.ibm.websphere.wim.exception.WIMConfigurationException: CWWIM5014E LDAP entity type PersonAccount is not found
Problem conclusion
Changed wp-update-standalone-ldap task. Failing Module(s): SECURITY Affected Users: All Users Version Information: Portal Version(s): 6.1.0.1 Pre-Requisite(s): PK82301 PK83085 Co-Requisite(s): --- Platform Specific: This fix applies to all platforms. A fix is available from Fix Central: http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorde r?apar=PK84702&productid=WebSphere%20Portal&brandid=5 You may need to type or paste the complete address into your Web browser.
Temporary fix
Comments
APAR Information
APAR number
PK84702
Reported component name
WEBSPHERE PORTA
Reported component ID
5724E7699
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-04-15
Closed date
2009-07-16
Last modified date
2009-11-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBSPHERE PORTA
Fixed component ID
5724E7699
Applicable component levels
R61A PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSHRKX","label":"WebSphere Portal"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1.0.1","Edition":"","Line of Business":{"code":"LOB31","label":"WCE Watson Marketing and Commerce"}}]
Document Information
Modified date:
11 February 2022