PH09574: PI97974 WAS ABOUT LDAP SEARCH FILTER ISSUE, WHICH DID NOT HANDLE PARENTHESIS CORRECTLY.

9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
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

• PI97974 was about LDAP Search filter issue, which did not
  handle parenthesis correctly.
   LdapRegistryI 3
  CN=xxxxx\(rtp\),CN=Users,dc=wasl3sec2,dc=raleigh,dc=ibm,dc=com:
  [LDAP: error code 34 - 0000208F: LdapErr: DSID-0C090787,
  comment: rror processing name, data 0, v1db1
  -----
  After upgrading from version 9.0.0.7 to 9.0.0.10, user searches
  fail in both the administrative console and the systems,
  apparently by the character parentheses '(' ')' -  \(xyz1\) in
  the DN of the entries in the LDAP directory. With the rollback
  to FP 7 the authentication works again.
  Exception stack
   LdapRegistryI E  SECJ0352E: Could not get the users matching
  the pattern cn=my UserName  \(xyz1\),ou=Users,o=IBM,o=com
  because of the following exception
  javax.naming.InvalidNameException: cn=my UserName
  \(xyz1\),ou=Users,o=IBM,o=com: [LDAP: error code 34 - Invalid
  DN Syntax]; remaining name 'cn=my UserName
  \(xyz1\),ou=Users,o=IBM,o=com'
      at
  com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3105)
      at
  com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2903)
      at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1858)
      at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1781)
      at
  com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentD
  irContext.java:404)
      at
  com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(Parti
  alCompositeDirContext.java:370)
      at
  org.apache.aries.jndi.DelegateContext.search(DelegateContext.jav
  a:360)
      at
  javax.naming.directory.InitialDirContext.search(InitialDirContex
  t.java:287)
      at
  com.ibm.ws.security.registry.ldap.LdapRegistryImpl.performAuthen
  tication(LdapRegistryImpl.java:2262)
      at
  com.ibm.ws.security.registry.ldap.LdapRegistryImpl.search(LdapRe
  gistryImpl.java:2233)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: LDAP user search fails when the         *
  *                      user's DN includes parenthesis          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Due to side effect of PI97974 (included in 9.0.0.10 and
  8.5.5.15), LDAP search for the user whose DN name includes
  parenthesis fails. It is due to unnecessary escape character
  in the DN.
  

Problem conclusion

• The bug has been fixed.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.16 and 9.0.5.0. 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 is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP

• R900 PSY

     UP