Uploaded image for project: 'JBoss Core Services'
  1. JBoss Core Services
  2. JBCS-1133

Increase commonName_max of openssl.cnf

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Blocker
    • None
    • httpd 2.4.37 SP7 GA
    • openssl
    • None
    • False
    • False
    • Undefined
    • Workaround Exists
    • Hide

      Provide your own properly generated cert

      Show
      Provide your own properly generated cert

    Description

      With a long FQDN, default cert generation from our postinstall fails with the following:

      string is too long, it needs to be no more than 64 bytes long
      

      So then start up after install fails out of the box with the following error:

      SSLCertificateFile: file '/opt/rh/jbcs-httpd24/root/etc/pki/tls/certs/localhost.crt' does
      not exist or is empty
      

      Would we consider increasing commonName_max in our openssl.cnf?

      Attachments

        Activity

          People

            dsoumis Dimitris Soumis
            rhn-support-aogburn Aaron Ogburn
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: