IBM Support

PI79888: An sslRef on an LDAPRegistry without matching ssl config causes security init failure

Fixes are available

17.0.0.2: WebSphere Application Server Liberty 17.0.0.2
17.0.0.3: WebSphere Application Server Liberty 17.0.0.3
17.0.0.4: WebSphere Application Server Liberty 17.0.0.4
18.0.0.1: WebSphere Application Server Liberty 18.0.0.1
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
20.0.0.6: WebSphere Application Server Liberty 20.0.0.6
20.0.0.7: WebSphere Application Server Liberty 20.0.0.7
20.0.0.8: WebSphere Application Server Liberty 20.0.0.8
20.0.0.9: WebSphere Application Server Liberty 20.0.0.9
20.0.0.10: WebSphere Application Server Liberty 20.0.0.10
20.0.0.11: WebSphere Application Server Liberty 20.0.0.11
20.0.0.12: WebSphere Application Server Liberty 20.0.0.12
21.0.0.3: WebSphere Application Server Liberty 21.0.0.3
21.0.0.4: WebSphere Application Server Liberty 21.0.0.4
21.0.0.5: WebSphere Application Server Liberty 21.0.0.5
21.0.0.6: WebSphere Application Server Liberty 21.0.0.6
21.0.0.7: WebSphere Application Server Liberty 21.0.0.7
21.0.0.8: WebSphere Application Server Liberty 21.0.0.8
21.0.0.9: WebSphere Application Server Liberty 21.0.0.9
21.0.0.1: WebSphere Application Server Liberty 21.0.0.1
21.0.0.2: WebSphere Application Server Liberty 21.0.0.2
21.0.0.10: WebSphere Application Server Liberty 21.0.0.10
21.0.0.11: WebSphere Application Server Liberty 21.0.0.11
21.0.0.12: WebSphere Application Server Liberty 21.0.0.12
22.0.0.1: WebSphere Application Server Liberty 22.0.0.1
22.0.0.2: WebSphere Application Server Liberty 22.0.0.2
22.0.0.3: WebSphere Application Server Liberty 22.0.0.3
22.0.0.4: WebSphere Application Server Liberty 22.0.0.4

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If the server.xml has an LDAPRegistry configuration with an
    sslRef defined with sslEnabled=false, but the sslRef points
    to a non-existent ssl configuration, the security service
    fails to start.  The message.log or FFDC errors include
    
    CWWKS3005E: A configuration exception has occurred. No
    UserRegistry implementation service is available.  Ensure
    that you have a user registry configured.
    FFDC1015I: An FFDC Incident has been created:
    "com.ibm.ws.security.registry.RegistryException: CWWKS3005E:
    A configuration exception has occurred. No UserRegistry
    implementation service is available.  Ensure that you have a
    user registry configured.
    com.ibm.ws.security.authentication.jaas.modules.TokenLoginMo
    dule 84" at ffdc_....log
    
    For example, if the LDAPRegistry includes sslEnabled=false
    (or no sslEnabled flag) and a sslRef="myLDAPSSLSettings" and
    the server.xml does not include an ssl configuration with
    the name, myLDAPSSLSettings, then security initialization
    can fail.
    
    To workaround, remove the sslRef.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty who set up an LDAPRegistry   *
    *                  without ssl enabled, but have an sslRef     *
    *                  defined                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: An sslRef on an LDAPRegistry without    *
    *                      matching ssl config causes security     *
    *                      init failure                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If the server.xml has an LDAPRegistry configuration with an
    sslRef defined with sslEnabled=false, but the sslRef points to a
    non-existent ssl configuration, the security service fails to
    start.  The message.log or FFDC errors include
    
    CWWKS3005E: A configuration exception has occurred. No
    UserRegistry implementation service is available.  Ensure that
    you have a user registry configured.
    
    FFDC1015I: An FFDC Incident has been created:
    "com.ibm.ws.security.registry.RegistryException: CWWKS3005E: A
    configuration exception has occurred. No UserRegistry
    implementation service is available.  Ensure that you have a
    user registry configured.
    com.ibm.ws.security.authentication.jaas.modules.TokenLoginModule
    84" at ffdc_....log
    
    For example, if the LDAPRegistry includes sslEnabled=false (or
    no sslEnabled flag) and a sslRef="myLDAPSSLSettings" and the
    server.xml does not include an ssl configuration with the name,
    myLDAPSSLSettings, then security initialization can fail.
    
    To workaround, remove the sslRef.
    

Problem conclusion

  • An extra sslRef on the LDAPRegistry configuration is ignored and
    security service initializes.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 170.0.0.2.  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

    PI79888

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-04-12

  • Closed date

    2017-04-13

  • Last modified date

    2017-04-13

  • 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

    LIBERTY PROFILE

  • Fixed component ID

    5724J0814

Applicable component levels

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

Document Information

Modified date:
04 May 2022