IBM Support

PK76493: Cross repository group member can not be shown properly.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Cross repository group member can't be shown properly.
    
    The problem is that when this wsadmin command is run it lists
    out    "Entity,null" instead of the local user that is listed as
    a member of the LDAP group:
    ----------------------------------------------------------------
    -----
    wsadmin>$AdminTask getMembersOfGroup {-uniqueName
    cn=ProcessOwnerGroup,
    o=groups}
    "PersonAccount, uid=DBUser,o=groups"
    "Entity, null"
    ----------------------------------------------------------------
    -----
    
    1.  Is this a support configuration, listing users from one
    repository in a group that exists on another repsoitory.
    2.  If this is a supported configuration, why do we return
    "Entity,null"  instead of the user?
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of WebSphere Application Server   *
    *                  v6.1 and v7.0 who use federated             *
    *                  repositories (virtual member manager).      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Cross repository group member can't     *
    *                      be listed properly.                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If you configured a cross repository group membership with
    database repository support, when retrieving members of the
    group entity stored in database repository, this group's
    members stored in LDAP repository can not be returned
    successfully.
    

Problem conclusion

  • This problem has been fixed, the cross repository members
    stored in LDAP repository can be listed successfully when
    getting all the members of one database group.
    
    The fix for this APAR is currently targeted for inclusion in
    fixpack 6.1.0.23 and 7.0.0.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

    PK76493

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    61A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-11-26

  • Closed date

    2008-12-01

  • Last modified date

    2008-12-02

  • 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

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

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

Document Information

Modified date:
29 December 2021