IBM Support

PM66752: CANNOT ENABLE FIPS 140-2, FAILS TO VALIDATE VALID SSL CERTIFICATE.

Fixes are available

7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
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.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When trying to enable Federal Information Processing
    Standard (FIPS) 140-2,
    all SSL certificates are checked to make sure they meet FIPS
    security standards, and can be converted if they do not.
    
    In some cases, the SSL certificate is valid, and shows so in
    traces, but is still showing invalid in the console.
    
    [6/13/12 13:34:16:333 UTC] 00000019 FIPSUtils     <
    initFipsecurityMode
    Exit
    FIPS 140-2
    [6/13/12 13:34:16:333 UTC] 00000019 ListCertStatu 3
    keyType:RSA
    keySize:2048. Minimum compliant keySize:1024
    [6/13/12 13:34:16:333 UTC] 00000019 ListCertStatu <
    evaluateKeySizeForFips: MEET_SECURITY_STANDARD Exit
    [6/13/12 13:34:16:333 UTC] 00000019 ListCertStatu >  mergeResult
    this.returnCode=3 this.reason= anotherReturnCode=3
    anotherReason= Entry
    [6/13/12 13:34:16:333 UTC] 00000019 ListCertStatu <  mergeResult
    Exit
    MEET_SECURITY_STANDARD
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server who enable FIPS after 7.0.0.23 and   *
    *                  8.0.0.3                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: When there is certificate that is not   *
    *                      signed by WebSphere Application         *
    *                      Server, the Server does                 *
    *                      not allow enabling FIPS.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When there is certificate that is not
    signed by WebSphere Application Server, if that
    certificate meets the FIPS requirement,
    the Application Server does not allow enabling FIPS.
    

Problem conclusion

  • The code is updated so that when certificate meets the
    specified FIPS standard, enableFIPS works regardless of who
    signed the ceritificate.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.25, 8.0.0.4, 8.5.0.1.  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

    PM66752

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-06-13

  • Closed date

    2012-07-05

  • Last modified date

    2012-07-05

  • 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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 October 2021