IBM Support

PI18352: VMM MAKES TOO MANY LDAP JNDI CALLS WITH IBM-ALLGROUPS CONFIGURED.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If ibm-allGroups is configured virtual member manager (VMM)
    does an additional validation for the groups which requires
    extra JNDI calls, which has an impact on the login process.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty Profile virtual member       *
    *                  manager (VMM)                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: If ibm-allGroups is configured VMM      *
    *                      does an additional validation for the   *
    *                      groups that are being returned from     *
    *                      the LDAP which requires extra JNDI      *
    *                      calls, which has an impact on login     *
    *                      time.                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If ibm-allGroups is configured VMM explicitly validates each
    group that is being returned from the LDAP as a value of the
    ibm-allGroups operational attribute to make sure that each and
    every entry that is being returned is actually a group not a
    user. This additional validation requires a JNDI call for each
    of the entries that needs to be validated which will have an
    impact in the overall login time.
    

Problem conclusion

  • VMM no longer does the additional validation of the groups
    that are being returned whenever ibm-allGroups is configured
    and returns the data that is being returned from backend LDAP
    directly to the user.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.3. 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

    PI18352

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-05-21

  • Closed date

    2014-07-01

  • Last modified date

    2014-07-01

  • 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

    LIBERTY PROFILE

  • Fixed component ID

    5724J0814

Applicable component levels

  • 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":"850","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 April 2022