IBM Support

PI88438: When defining a root Base DN for a federated repository, display and login problems occur

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When adding multiple repositories to a federated repository,
    including a "root" or empty base entry, login problems can
    occur. Additionally, the list of "Repositories in the realm:" on
    the "Federated repositories" page in the Information Center
    console is incorrect. It lists duplicate entries of the non-root
    LDAP server and the root LDAP server is missing.
    

Local fix

  • Alter the order you add the repositories to the list may allow
    the repositories to be added normally.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server using Federated Repositories (VMM)   *
    *                  and defining the base DN or participating   *
    *                  Base Entry of an LDAP server as "root" or   *
    *                  an empty base DN (indicating the entire     *
    *                  LDAP                                        *
    *                  tree).                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: When defining a root Base DN for a      *
    *                      federated repository, display and       *
    *                      login problems occur                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When adding multiple repositories to a federated repository,
    including a "root" or empty base entry, login problems can
    occur. Additionally, the list of "Repositories in the realm:"
    on the "Federated repositories" page in the administrative
    console is incorrect. It lists duplicate entries for the
    non-root LDAP server and the root LDAP server is missing.
    

Problem conclusion

  • The code was fixed so the "best match" policy is maintained with
    a root or empty base entry (DN) during unique name look ups.
    
    The console was also fixed to correctly display all
    participating base entries.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.0.0.15, 8.5.5.14 and 9.0.0.8.  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

    PI88438

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-10-05

  • Closed date

    2017-11-28

  • Last modified date

    2018-04-15

  • 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

  • R800 PSY

       UP

  • R850 PSY

       UP

  • R900 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 850

Reference #: PI88438

Modified date: 15 April 2018


Translate this page: