PM88674: LDAP SEARCH MIGHT FAIL WHEN BASE DN IS SET AS BLANK.

Fixes are available

APAR status

Closed as program error.

Error description

Not able to login as the error in log shows
[datetime] 00000032 LTPAServerObj > authenticate
1670210445 Entry
BasicAuthData:
userid=CN=FirstName
LastName/DC=Test,password=xxxxxxx,realm=
[datetime] 00000032 LdapRegistryI 3 "CN=FirstName
LastName/DC=Test": [LDAP: error code 34 - Invalid DN Syntax]
The following conditions will cause this error to occur:
- Standalone LDAP is enabled
- The LDAP server type is Domino or a Custom LDAP which
utilizes a blank base entry.
- An attribute is utilized in the userFilter that contains the
full distinguished name (DN) of the user.
This is a unique situation, this problem happens since base DN
is set as blank. Therefore the LDAP code cannot determine
properly whether given string is DN or not.

Local fix

Update the standalone LDAP configuration by removing the
attribute which contains the full distinguished name of the
user from the userFilter.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: Standalone LDAP user registry might     *
*                      fail to lookup users when base DN       *
*                      isn't set.                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When Standalone LDAP user registry is used and base DN isn't
set, user lookup might fail because the code selects
incorrect lookup method for LDAP server.

Problem conclusion

With this fix, user lookup is performed with proper method.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.31, 8.0.0.8, and 8.5.5.2.  Please refer to the
Recommended Updatespage for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM88674
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-05-08
Closed date
2013-09-27
Last modified date
2013-09-27

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
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

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 April 2022

Tips

PM88674: LDAP SEARCH MIGHT FAIL WHEN BASE DN IS SET AS BLANK.

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

R700 PSY

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?