IBM Support

PI71926: BIND DN NOT SAVED CORRECTLY WHEN EDITING SECURITY CONFIGURATION

Fixes are available

9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When clicking on the solutions console OK button under the
    following path causes error.
    
    Global security > Federated repositories >Myldap
    
    CWWIM5020E Could not connect to the
    ldap://myldapserver.domain.com:389 repository using properties:
    ...Exception
    occurred: javax.naming.AuthenticationException.
    
    Since the bind password is pre-populated incorrectly in the
    VMM  page, the 'LDAP test query' page also gets pre-populated
    with the incorrect password and no query is successful.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    *                  who access the 'LDAP Test Query' page after *
    *                  configuring a federated repository on the   *
    *                  VMM                                         *
    *                  page.                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: The 'Bind password' is pre-populated in *
    *                      the LDAP page with the same value used  *
    *                      in                                      *
    *                      the VMM page and it's causing errors.   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If the user clicks the Apply/Ok button under the following
    path, an authentication exception is thrown.
    Global security > Federated repositories >Myldap
    This occurs because the 'Bind password' field is being pre-
    populated with the string "*******". When changes are applied,
    the obfuscated password is passed in as the value for the
    password parameter causing an authentication error. Since the
    'LDAP test query' page pre-populates the 'Bind password' field
    the same way the VMM page does, the queries are also failing.
    To provide another level of security and to avoid issues with
    the password, we have made the 'Bind password' a required field
    in the 'LDAP test query' page. It will no longer be pre-
    populated. The VMM panel password issue was fixed under
    PI72154.
    

Problem conclusion

  • To provide another level of security and to avoid issues with
    the password, we have made the 'Bind password' a required field
    in the 'LDAP test query' page. It will no longer be pre-
    populated and the user must know the correct bind password in
    order to run a query. The VMM panel password issue was fixed
    under PI72154.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.43, 8.0.0.13, 8.5.5.12, and 9.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

    PI71926

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-11-07

  • Closed date

    2016-12-19

  • Last modified date

    2017-03-06

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP

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

Document Information

Modified date:
04 May 2022