IBM Support

JR47589: JS API CALL HASUSER ON PARTICPANTGROUPSCRIPTABLE DOES NOT REFLECT LDAP USER MEMBERSHIPS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • JS API call hasUser on ParticpantGroupScriptable does not
    reflect LDAP user memberships.
    .
    When performing the js api call hasUser on
    ParticipantGroupScriptable, the user memberships are checked in
    the BPM user repository, but not in an LDAP directory configured
    for Federated Repositories. In case a user has not logged into
    BPM before, user memberships will not reflect the memberships
    defined in the LDAP server.
    

Local fix

Problem summary

  • TWParticipantGroup.hasUser() should synchronize this one LDAP
    user, and respect the LDAP group memberships.
    
    PROBLEM DETAILED DESCRIPTION:
    Customers who use LDAP groups within their participant group
    definitions and use Java Script API method "hasUser" experience
    the following behavior, which has been in effect for many years:
    
    1. LDAP groups are synchronized to BPM-DB at server startup
    2. LDAP users are synchronized to BPM-DB via the Process Admin
       Console > User Synchronization > Full Synchronize button
    3. LDAP group memberships are synchronized to BPM-DB when the
       user logs into BPM.
    
    TWParticipantGroup.hasUser() works correct only, when all three
    items have been successfully synchronized.
    

Problem conclusion

  • TWParticipantGroup.hasUser() has been enhanced.
    
    FIX AVAILABILITY:
    iFix for 7.5.1.1 is available on Fix Central, search for APAR
    JR47589 at http://www.ibm.com/support/fixcentral/
    iFix for 8.5.0.0 is available on Fix Central, search for APAR
    JR47589 at http://www.ibm.com/support/fixcentral/
    Fix is also targetted for inclusion in next fixpack for BPM
    V7.5.1, BPM 8.0.1, BPM 8.5.0
    
    When obtaining any of the above fixes, be sure to download the
    accompanying readme, for itself, and any prerequisite fixes, and
    review them thorougly.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR47589

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    751

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-08-21

  • Closed date

    2013-11-14

  • Last modified date

    2013-11-14

  • 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

    BPM STANDARD

  • Fixed component ID

    5725C9500

Applicable component levels

  • R750 PSY

       UP

  • R751 PSY

       UP

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
14 November 2013