PI81497: When one base DN is the subset of another in a federated repository, LDAP failures occur.

Fixes are available

APAR status

Closed as program error.

Error description

When on base DN is the subset of the other, federated
repository does not access to the LDAP even though these two
LDAP servers are independent.

Following is the example of base DNs which hits the issue;

<participatingBaseEntry name="ou=abc,o=xyz.com"/>
<participatingBaseEntry name="o=xyz.com"/>

With this configuration, users on the LDAP with base DN of
"ou=abc,o=xyz.com" fail to be authenticated because
federated
repository does not access to to the LDAP.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server - Virtual Member Manager             *
*                  (VMM)                                       *
****************************************************************
* PROBLEM DESCRIPTION: When one base DN is a subset of         *
*                      another                                 *
*                      base DN in a federated repository,      *
*                      failures may occur.                     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When choosing which repository an entity belongs to, we were
returning the first repository that matches the trailing RDNs
of
any base DN.
Following is the example of base DNs which hits the issue;
<participatingBaseEntry name="ou=abc,o=xyz.com"/>
<participatingBaseEntry name="o=xyz.com"/>
With this configuration, users on the LDAP with base DN of
"ou=abc,o=xyz.com" fail to be authenticated.

Problem conclusion

We now search every repository to ensure we find a best match.

The fix for this APAR is currently targeted for inclusion in
fix packs 8.0.0.14, 8.5.5.12, 9.0.0.5, and fix pack 17.0.0.3
for WebSphere Application Server Liberty.
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
PI81497
Reported component name
WAS LIBERTY COR
Reported component ID
5725L2900
Reported release
CD0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-05-11
Closed date
2017-08-02
Last modified date
2017-10-12

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
WAS LIBERTY COR
Fixed component ID
5725L2900

Applicable component levels

RCD0 PSY
UP

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

Document Information

Modified date:
04 May 2022

Tips

PI81497: When one base DN is the subset of another in a federated repository, LDAP failures occur.

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

RCD0 PSY

Document Information

Share your feedback

Need support?