PM82405: ATTRIBUTE CACHE IN FEDERATED REPOSITORIES HANDLES DISTINGUISHED NAME AS CASE INSENSITIVE.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Attribute cache in federated repositories is used to minimize
    performance impacts by maintaining internal caches of retrieved
    data. The attribute cache handles Distinguished Name(DN) as
    case insensitive. Therefore, federated repositories handles
    users which are different in case sensitive matching rule as a
    same user when LDAP server is configured to handle DN as case
    sensitive.
    
    For example, following two users are handled as a same user;
    
    uid=ABC,O=IBM,C=US
    uid=abc,O=IBM,C=US
    
    This problem occurs when these two users access within
    attribute cache time-out.
    

Local fix

  • Disable attribute cache
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: VMM handles user DN which have          *
    *                      different case in LDAP as the same      *
    *                      user when attribute cache is enabled.   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    LDAP server handles users DN as case sensitive, but VMM
    handles users which are different in case,but with the same
    DN as the same user when attribute cache is enabled.
    

Problem conclusion

  • To fix this, you need to set a new custom property
    "caseSensitiveDNForAttributeCache" with value "true". This
    will return DN in case sensitivity simialr to the value that
    exists in the LDAP repository when attribute cache is also
    enabled.
    
    In order to set this property, use the following command:
    
    $AdminTask setIdMgrCustomProperty {-id <LDAP_repos_ID> -name
    caseSensitiveDNForAttributeCache -value true}
    
    Here "LDAP_repos_ID" is the repository id of the LDAP
    configured in VMM.
    Also save the configuration after running the previous command
    using:
    
    $AdminConfig save
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.31, 8.0.0.8 and 8.5.5.1.  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

    PM82405

  • 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-02-08

  • Closed date

    2013-06-28

  • Last modified date

    2013-06-28

  • 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



Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Application Server
General

Software version:

7.0

Reference #:

PM82405

Modified date:

2013-06-28

Translate my page

Machine Translation

Content navigation