Direct links to fixes
Closed as program error.
When configuring stand-alone LDAP as a WebSphere Application Server user registry, IBM BPM synchronizes user information stored in LDAP incorrectly, by extracting user distinguished names from LDAP and inserts them as user names into the IBM BPM database. As a consequence, users cannot log in with the names they expect to use.
This issue occurs because the twUserNameAttribute configuration setting is not honored.
A fix that ensures the configuration setting is correctly evaluated and reflected is planned - to be made available for IBM BPM V126.96.36.199, V188.8.131.52, and V184.108.40.206 - to be included in a future fix pack for IBM BPM V8.5.0 - to be included in an IBM BPM V220.127.116.11 cumulative fix On Fix Central (http://www.ibm.com/support/fixcentral), search for JR54207: 1. Select IBM Business Process Manager with your edition from the product selector, the installed version to the fix pack level, and your platform, and then click Continue. 2. Select APAR or SPR, enter JR54207, and click Continue. When you download fix packages, ensure that you also download the readme file for each fix. Review each readme file for additional installation instructions and information about the fix. To set the value for this property, see ?Security configuration properties (http://www.ibm.com/support/knowledgecenter/SSTLXK_8.5.6/com.ibm .wbpm.imuc.ebpm.doc/topics/csec_config_properties.html).
Reported component name
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels
26 November 2015