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

Fixes are available

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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021

Tips

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

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?