IBM Support

PI80721: WEBSPHERE DEFAULT CHAINED CERTIFICATE DOESN'T HAVE DNS NAMES UNDER SUBJECT ALTERNATIVE NAME FIELD

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Chrome now requires certificates to have the DNS names listed
    in the Subject Alternative Name field and ignores DNS entries
    in Subject field of a certificate
    
    Chrome requires a DNS SAN to be set to the hostname of the
    server in the request
    
    Our Websphere default chained certificate that are being
    generated do not have a DNS under  Subject Alternative Name
    entry.
    
    Note that RFC 2818 has deprecated the use of hostname matching
    via the CN entry of the subject and encouraging all CAs to use
    Subject
    Alternative Naming:
    
       If a subjectAltName extension of type dNSName is present,
    that MUST be used as the identity. Otherwise, the (most
    specific) Common Name field in the Subject field of the
    certificate MUST be used. Although    the use of the Common
    Name is existing practice, it is deprecated and
    Certification Authorities are encouraged to use the dNSName
    instead.
    

Local fix

  • create a self singed certificate with DNS under SAN
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    *                  And users of Google Chrome Browser          *
    ****************************************************************
    * PROBLEM DESCRIPTION: After upgrading to Chrome Build 58 I    *
    *                      get a                                   *
    *                      security error saying that my           *
    *                      certificate                             *
    *                      is not valid due to missing Subject     *
    *                      Alternate Name (SAN)                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    After upgrading to Chrome Build 58 I get a security error saying
    that my certificate is not valid due to missing Subject
    Alternate
    Name (SAN)
    

Problem conclusion

  • The code was reviewed and updated and a new custom property was
    introduce "com.ibm.websphere.security.addSANToSSLCertificate" th
    when enabled, all certificates created afterwards will include t
    following default SAN values:
    
    Email: "user@domain"
    Domain Name: <Certificate_Subject_DN_Name>
    URL: http:// <Certificate_Subject_DN_Name>
    IP Address: 127.0.0.1
    URL: http:// <Certificate_Subject_DN_Name>
    
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.13, 9.0.0.6.  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

    PI80721

  • 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

    2017-04-27

  • Closed date

    2017-10-02

  • Last modified date

    2017-10-02

  • 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

  • R850 PSY

       UP

  • R900 PSY

       UP

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

Document Information

Modified date:
07 September 2021