PQ92550: Active Directory LDAP returns invalid XML character reference to null, causes SOAP exception in Web Service client

 Fixes are available

5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for AIX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Windows
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for HP-UX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Solaris
5.1.1.6: WebSphere Application Server Version 5.1.1 Cumulative Fix 6
5.1.1.7: WebSphere Application Server Version 5.1.1 Cumulative Fix 7
5.1.1.4: WebSphere Application Server Version 5.1.1 Cumulative Fix 4
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Linux



APAR status
Closed as program error.

Error description
User enters invalid userid or password on client to Active
Directory server. LDAP server returns "&#0", a reference
to a null, which is invalid in XML.  Error seen at client:
javax.xml.soap.SOAPException: org.xml.sax.SAXParseException:
Character
reference "�" is an invalid XML character. To see the message
containing the parsing error in the log, either enable web
service
engine tracing or set MessageContext.setHighFidelity(true).
at
com.ibm.ws.webservices.engine.soap.SOAPConnectionImpl.call(SOAPC
onnectio
nImpl.java:124)
at test.ClientwithSoapHdr.main(ClientwithSoapHdr.java:83)
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users       *
****************************************************************
* PROBLEM DESCRIPTION: The faultString portion of the          *
*                      SOAPFault allows invalid XML characters *
*                      in the string.                          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
In some cases, a null or invalid character reference was being
returned as part of the fault string.  This wasn't a problem
for the server, but when the response gets back to the client,
a SAXParseException is thrown.  The character returned is
actually an invalid XML character.
Problem conclusion
We've corrected this by adding in standard mappings for the
invalid characters.
Temporary fix Comments
APAR information
APAR number PQ92550
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00W
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-08-06
Closed date 2004-09-30
Last modified date 2004-09-30

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
WEBSVCS          

Publications Referenced

Fix information

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00P PSY    UP
R00S PSY    UP
R00W PSY    UP
R103 PSY    UP
R10A PSY    UP
R10H PSY    UP
R10I PSY    UP
R10P PSY    UP
R10S PSY    UP
R10W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ92550
IBM Group: Software Group
Modified date: Sep 30, 2004