Select Your Language

Infrastructure and Management

Cloud Computing

Storage

Runtimes

Integration and Automation

  • Comments
  • Puppet SSL CA names are identical post satellite-installer?

    Posted on

    Both the CN and CA CN have the same name?

    openssl s_client -connect :8140
    

    Prior to this I ran the installer; I needed to add a custom SSL cert to satellite:
    Red Hat Satellite (build: 6.3.4)

        satellite-installer --scenario satellite\
                          --certs-server-cert "/etc/pki/tls/certs/localhost.crt"\
                          --certs-server-cert-req "/root/custom_ssl/localhost_csr.pem"\
                          --certs-server-key "/etc/pki/tls/private/localhost.key"\
                          --certs-server-ca-cert "/root/custom_ssl/custom_ssl.pem"\
                          --certs-update-server --certs-update-server-ca --certs-update-all
    

    It seems like puppet didn't get the CA I specified? I can remedy this if I knew
    the location of the puppet CA. Running openssl on 8140 I can see the problem,
    but I have been having trouble tracking down the .pem file. The install went off without a hitch it's just this annoying little CN conflict I need to knock out.

    by

    points

    Responses

    Red Hat LinkedIn YouTube Facebook X, formerly Twitter

    Quick Links

    Help

    Site Info

    Related Sites

    © 2026 Red Hat