IBM Support

PH31613: GSSAPI/Kerberos Ldap bind authentication support for LDAP

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Only simple authentication (user/password) was supported for
    binding to the Ldap server. Support for bind to
    the Ldap server using GSSAPI/Kerberos is added for both
    standalone Ldap and federated repositories.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    *                  who would like to use Kerberos to bind to   *
    *                  the                                         *
    *                  Ldap server.                                *
    ****************************************************************
    * PROBLEM DESCRIPTION: Previously, the user could only supply  *
    *                      the bindDN and bindPassword (or do an   *
    *                      anonymous bind) to bind to the Ldap     *
    *                      server.                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Previously, the user could only supply the bindDN and
    bindPassword
    (or do an anonymous bind) to bind to the Ldap server. Customers
    would like to use GSSAPI/Kerberos and supply a Kerberos
    principal
    name or Kerberos service principal name and either a
    ticketCache/ccache or keytab to bind to the
    Ldap
    for user and group searches/etc.
    

Problem conclusion

  • Both standalone Ldap and federated repositories configurations
    were updated to support GSSAPI/Kerberos bind authentication to
    the Ldap server. Users can configure Kerberos using the
    administrative console or wsadmin. The Kerberos principal name
    or Kerberos service principal name
    can be authenticated using either a ticketCache (ccache) or a
    keytab file.
    
    The fix for this APAR is targeted for inclusion in fix pack
    8.5.5.19 and 9.0.5.7. For more information, see 'Recommended
    Updates for WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH31613

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-11-13

  • Closed date

    2021-02-04

  • Last modified date

    2021-02-04

  • 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

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900"}]

Document Information

Modified date:
05 February 2021