Fixes are available
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
Information Server 11.3 is now shipping with Liberty profile. The productInfo version shows 8.5.5.1 running on Suse Linux 11.3. Both tivoli and AD filters are not working. There are no error with these filters, you simply get back all my users and all your groups when requesting a user/group list from your application. Adding the same filters to WebSphere Application Server Network Deployment edition standalone LDAP they behave correctly.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty Profile- Virtual Member * * Manager (VMM) * **************************************************************** * PROBLEM DESCRIPTION: Provide a way to configure an LDAP * * entity type specific search filter, * * search Base and an Object class * **************************************************************** * RECOMMENDATION: * **************************************************************** Prior to this fix, a Liberty profile user working with the LDAP registry did not have a way to configure an LDAP entity type specific search filter, search Base and an Object class. These were critical in order to narrow down the LDAP query to specific records. With this fix, it is possible to specify those attributes.
Problem conclusion
This fix will provide an extra configuration of LDAP entity type in LDAP registry by which user will be able to define new set of rules like search filter, search Base and an Object class. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.6. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI38554
Reported component name
LIBERTY PROFILE
Reported component ID
5724J0814
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-04-08
Closed date
2015-04-22
Last modified date
2015-04-22
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
LIBERTY PROFILE
Fixed component ID
5724J0814
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
28 April 2022