When Distinguished Names (DNs) in the LDAP server include special characters, logging in to authenticate or authorizing to access a secure resource fails

Technote (FAQ)
Problem
Logging in to authenticate or authorizing to access a secure resource fails when Distinguished Names (DNs) in the LDAP server include special characters. These special characters include: commas, semicolons, percent sign, asterisk, trailing space, and others.
Cause
Logging in to authenticate or authorizing to access a secure resource fails because WebSphere Application Server truncates the DNs at the special character.

.Environment:
WebSphere Application Server 3.5.4

Solution
This actually affects all versions of WebSphere Aplication Server 3.x up to 3.5.4, but interim fix PQ51768 has been created only for 3.5.4 to address this issue. The interim fix will allow special characters to be recognized.
Historical Number
PQ51768











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Security
Operating system(s): Multi-Platform
Software version: 3.5.4
Software edition: Standard, Advanced
Reference #: 1030969
IBM Group: Software Group
Modified date: 2003-05-01