Home
User Guide
The information contained in this section applies to IBM WebSphere Commerce Version 7.0.0.9 and Feautre Pack 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in new editions.
Installing
Review this section for information about installing the WebSphere Commerce product, associated maintenance, and WebSphere Commerce enhancements.
Installing maintenance
WebSphere Commerce maintenance includes installing fix packs, interim fixes (APARs), and cumulative interim fixes.
Interim fixes and cumulative interim fixes
A WebSphere Commerce interim fix (iFix) is a software patch that contains fixes for one or more APARs. A WebSphere Commerce cumulative iFix is a comprehensive collection of interim fixes for a specific release. Both types of fixes are installed with the WebSphere Commerce Update Installer (UPDI).
Additional steps for member or session management-related interim fixes
Some interim fixes include changes that affect login or session management. After you install the fix, you might need to complete additional steps to enable the fix on your environment.
Enabling interim fix JR52717
JR52717 fixes an issue where the shopper registration fails if the LDAP server is enabled with UserAccountValue 512 and 544. APAR JR45992 changes the password policy validation logic, which, however, does not comply with the password policy of the LDAP server.

WebSphere Commerce Version 7.0.0.9

Enabling interim fix JR52717

JR52717 fixes an issue where the shopper registration fails if the LDAP server is enabled with UserAccountValue 512 and 544. APAR JR45992 changes the password policy validation logic, which, however, does not comply with the password policy of the LDAP server.

Before you begin

Install the interim fix for JR52717.

For information about how to install an interim fix, see

About this task

To comply the password policy of the LDAP server:

Note: This solution can solve the problem caused by enabling UserAccountControl as 512 and 544 on the LDAP server. However, for LDAP servers such as TDS, you may also enable the security restriction (pwdMinAge) that limits the interval of operating password attribute. This APAR operates password attribute twice in a very short time by two transactions. Thus if you also enable pwdMinAge, reduce the interval.

Procedure

Go to the workspace_dir\WC\xml\config directory.

Add the following in the wc-server.xml file:

MemberSubSystem AuthenticationMode="LDAP" ProfileDataStorage="LDAP">
             ...
            <SyncPassword syncPasswordInSyncBeanEnabled="true"/>
             ...
        </MemberSubSystem>