<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    So for our internal yum server, I created a new key and cert request
    (it had a localhost key and cert but I wanted to start clean):<br>
    <blockquote><tt># openssl genrsa 2048 >
        /etc/pki/tls/private/server.key</tt><br>
      <tt># openssl req -new -x509 -nodes -sha1 -days 365 -key
        /etc/pki/tls/private/server.key >
        /etc/pki/tls/certs/server.crt</tt><br>
      <tt># ipa-getcert request -f /etc/pki/tls/certs/server.crt -k
        /etc/pki/tls/private/server.key -r</tt><br>
    </blockquote>
    ipa-getcert list shows it approved. I set up SSL in apache to use
    the above .key and .crt, but when I try to run yum against this
    using ssl:<font face="Courier New, Courier, monospace"><br>
    </font>
    <blockquote><tt># yum search ffmpeg</tt><br>
      <tt>Loaded plugins: langpacks</tt><br>
      <tt><a class="moz-txt-link-freetext" href="https://yum.private.net/fedora/releases/21/Everything/x86_64/os/repodata/repomd.xml">https://yum.private.net/fedora/releases/21/Everything/x86_64/os/repodata/repomd.xml</a>:
        [Errno 14] curl#60 - "Peer's certificate issuer has been marked
        as not trusted by the user."</tt><br>
      <tt>:</tt><br>
    </blockquote>
    Is there a step I need to take on the clients so they'll accept this
    cert as trusted? I thought having it be signed by the IPA CA would
    have taken care of that.<br>
    <blockquote><tt># ls -l /etc/ipa/ca.crt</tt><br>
      <tt>-rw-r--r-- 1 root root 2546 Apr 28  2014 /etc/ipa/ca.crt</tt><br>
      <tt>#</tt><br>
    </blockquote>
    ---<br>
    Bret<br>
    <br>
    <div class="moz-cite-prefix">On 06/02/2016 07:25 PM,
      <a class="moz-txt-link-abbreviated" href="mailto:bret.wortman@damascusgrp.com">bret.wortman@damascusgrp.com</a> wrote:<br>
    </div>
    <blockquote cite="mid:b0aa17ae-de3c-446f-8cab-48cace412554@Spark"
      type="cite">
      <title></title>
      <div name="messageBodySection">Cool. I'll give this a go in the
        morning.</div>
      <div name="messageSignatureSection"><br>
        Bret Wortman 
        <div><a class="moz-txt-link-freetext" href="http://wrapbuddies.co/">http://wrapbuddies.co/</a></div>
      </div>
      <div name="messageReplySection"><br>
        On Jun 2, 2016, 6:24 PM -0400, Fraser Tweedale
        <a class="moz-txt-link-rfc2396E" href="mailto:ftweedal@redhat.com"><ftweedal@redhat.com></a>, wrote:<br>
        <blockquote type="cite">On Thu, Jun 02, 2016 at 05:35:01PM
          -0400, <a class="moz-txt-link-abbreviated" href="mailto:bret.wortman@damascusgrp.com">bret.wortman@damascusgrp.com</a> wrote:<br>
          <blockquote type="cite">Sorry, let me back up a step. We need
            to implement hype<br>
            everywhere. All our web services. And clients need to get<br>
            keys&certs automatically whether through IPA or Puppet.
            These<br>
            systems use IPA for everything but authentication (to keep
            most<br>
            users off). I'm trying to wuss out the easiest way to make
            this<br>
            happen smoothly.<br>
            <br>
          </blockquote>
          Hi Bret,<br>
          <br>
          You can use the IPA CA to sign service certificates. See<br>
<a class="moz-txt-link-freetext" href="http://www.freeipa.org/page/Certmonger#Request_a_new_certificate">http://www.freeipa.org/page/Certmonger#Request_a_new_certificate</a>.<br>
          <br>
          IPA-enrolled machines already have the IPA certificate in
          their<br>
          trust store. If the clients are IPA-enrolled, everything
          should<br>
          Just Work, otherwise you can distribute the IPA CA certificate
          to<br>
          clients via Puppet** or whatever means you prefer.<br>
          <br>
          ** you will have to work out how, because I do not know Puppet
          :)<br>
          <br>
          Cheers,<br>
          Fraser<br>
          <br>
          <blockquote type="cite"><br>
            <br>
            On Jun 2, 2016, 5:31 PM -0400, Rob
            Crittenden<a class="moz-txt-link-rfc2396E" href="mailto:rcritten@redhat.com"><rcritten@redhat.com></a>, wrote:<br>
            <blockquote type="cite">Bret Wortman wrote:<br>
              <blockquote type="cite">Is it possible to use our freeipa
                CA as a trusted CA to sign our<br>
                internal SSL certificates? Our system runs on a private
                network and so<br>
                using the usual trusted sources isn't an option. We've
                been using<br>
                self-signed, but that adds some additional complications
                and we thought<br>
                this might be a good solution.<br>
                <br>
                Is it possible, and, since most online guides defer to
                "submit the CSR<br>
                to Verisign" or whomever, how would you go about
                producing one in this way?<br>
              </blockquote>
              <br>
              Not sure I understand the question. The IPA CA is also
              self-signed. For<br>
              enrolled systems though at least the CA is pre-distributed
              so maybe that<br>
              will help.<br>
              <br>
              rob<br>
              <br>
            </blockquote>
          </blockquote>
          <br>
          <blockquote type="cite">--<br>
            Manage your subscription for the Freeipa-users mailing list:<br>
            <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/freeipa-users">https://www.redhat.com/mailman/listinfo/freeipa-users</a><br>
            Go to <a class="moz-txt-link-freetext" href="http://freeipa.org">http://freeipa.org</a> for more info on the project<br>
          </blockquote>
          <br>
        </blockquote>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
    </blockquote>
    <br>
  </body>
</html>