IBM Support

PH43950: SETTING SSLENABLED ON CUSTOMREGISTRY RESULTS IN CLASSCASTEXCEPTION

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

  • When setting the sslEnabled property via Admin Console or wsadmi
    eg. AdminTask.setIdMgrCustomProperty( [-id racfldap -sslE
    value true] ), the following error occurs:
    
    [2/2/22 11:41:57:262 CET] 000000f6 LdapRegistryI E  SECJ0068E: L
    initialization error. The exception is
    java.lang.ClassCastException: java.lang.String incompatible with
    java.lang.Boolean
    at
    com.ibm.ws.security.registry.ldap.LdapConfig.getSSLEnabled(LdapC
    ig.java:281)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: When running                            *
    *                      AdminTask.setIdMgrCustomProperty(       *
    *                      [-id racfldap -sslE                     *
    *                      value true]) a                          *
    *                      ClassCastException is seeing on the     *
    *                      logs.                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When running
    AdminTask.setIdMgrCustomProperty(
    [-id racfldap -sslE
    value true]) a
    ClassCastException is seeing on the
    logs.
    

Problem conclusion

  • The code has been revised and updated to prevent this issue
    from happening in the future.
    
    The fix for this APAR is targeted for inclusion in fix pack
    9.0.5.11 and 8.5.5.21. 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

    PH43950

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-02-09

  • Closed date

    2022-02-22

  • Last modified date

    2022-03-07

  • 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

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

Document Information

Modified date:
08 March 2022