IBM Support

PI79781: FEDERATED REPOSITORIES FAILS TO SEARCH REPOSITORY WHEN OVERLAPPING BASE DN'S EXIST.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When Federated Repositories is configured with 2 different
    repositories whose base entries overlap, entities from one of
    the repositories may not be returned. An example of
    overlapping base entries is below.
    
        ou=users,dc=ibm,dc=com
                 dc=ibm,dc=com
    

Local fix

  • make sure each base entry is unique
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server users of   *
    *                  federated repositories                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: When two or more repositories have      *
    *                      overlapping base entries, federated     *
    *                      repositories may ignore some of the     *
    *                      repositories.                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    On initialization Federated Repositories checks participating
    base entries of the repositories agains the defined
    repositories. When doing so, it was doing a greedy search
    where the first repository whose base entry ended with the
    particpating base entry would claim that participating base
    entry. This resulted in one repository claiming the
    participating base entries that were intended to include other
    repositories.
    

Problem conclusion

  • The logic for claiming repositories for each participating
    base entry was updated to find a 'best' repository match
    instead of using the first repository that only
    partcially matches.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.14, 8.5.5.12 and 9.0.0.5.  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

    PI79781

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-04-11

  • Closed date

    2017-06-05

  • Last modified date

    2017-06-05

  • 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

  • R800 PSY

       UP

  • R850 PSY

       UP

  • R900 PSY

       UP

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850"}]

Document Information

Modified date:
06 September 2021