IBM Support

PM64474: ESCAPE CHARACTER WAS NOT HANDLING CORRECTLY WHEN USING RACFID SEARCH FILTER

Fixes are available

7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When WSAS (LDAP) client is setup using zOS search filter,
    WebSphere Application Server security code was not handling the
    escaped \ that caused failure with exception.
    
    [4/26/12 12:56:11:045 PDT] 0000004e LdapRegistryI >  getUsers
    Entry
                                      \#L00540
                                      0
    [4/26/12 12:56:11:045 PDT] 0000004e LdapRegistryI >  search
    Entry
    [4/26/12 12:56:11:045 PDT] 0000004e LdapRegistryI 3   DN:
    cn=ibmldap
    [4/26/12 12:56:11:045 PDT] 0000004e LdapRegistryI 3   Search
    scope:
    2
    [4/26/12 12:56:11:045 PDT] 0000004e LdapRegistryI 3   Filter:
    (racfid=\\#L00540)
     ----------------
    [4/26/12 12:56:11:070 PDT] 0000004e LdapRegistryI 3   [LDAP:
    error code 80 - ICH31016I  INVALID CHARACTER IN FILTER STRING]
    
    [4/26/12 12:56:11:151 PDT] 0000004e LdapRegistryI E   SECJ0352E:
    Could not get the users matching the pattern \#L00540 because of
    the following exception javax.naming.NamingException: [LDAP:
    error code 80 - ICH31016I  INVALID CHARACTER IN FILTER STRING];
    remaining name
    'cn=ibmldap'
      at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3089)
      at
    com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2991)
      at
    com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2797)
      at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1849)
      at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1772)
      at
    com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentD
    irContext.java:383)
      at
    com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(Parti
    alCompositeDirContext.java:353)
      at
    javax.naming.directory.InitialDirContext.search(InitialDirContex
    t.java:268)
      at
    com.ibm.ws.security.registry.ldap.LdapRegistryImpl.search(LdapRe
    gistryImpl.java:2208)
    
    [4/26/12 12:56:11:155 PDT] 0000004e exception     E
    com.ibm.ws.wim.adapter.urbridge.URBridge
    getEntityTypeFromUniqueName CWWIM4001E The '\#L00540' entity was
    not found.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Standlone LDAP user registry does not   *
    *                      handle search string which contains     *
    *                      escaped chracters property.             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When standalone user registry is configured using zOS search
    filter, WebSphere Application Server security code was not
    handling the escaped character properly. This might cause
    an ldap lookup failure resulting in a user authentication
    failure.
    

Problem conclusion

  • With this fix, Standalone user registry code handles string
    which contains escaped characters properly.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 6.1.0.45, 7.0.0.25, 8.0.0.5. 8.5.0.1.  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

    PM64474

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-05-11

  • Closed date

    2012-06-20

  • Last modified date

    2012-07-17

  • 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

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM64474

Modified date: 17 July 2012