<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>To whom this may concern,</p>
<p>I use FreeIPA and I would like to create certificates for
peer-to-peer and remote-access VPNs. In speaking with Fraser
Tweedale, we agree that the best way forward is to create a
secondary CA for insulation; but we may also need to create a
custom certificate profile, which is non-trivial. As an end user
of FreeIPA, I would like documentation on how to do this.</p>
<p>I use pfSense which requires that I upload the CA cert, a server
cert and its private key. The private key for the CA is optional
and only required for pfSense to self manage a CRL. On the server
side I can also enforce the certificate depth; from none, to one
through five. <br>
</p>
<p>The only existing references to VPN in the current docs are:</p>
<p>* <a class="moz-txt-link-freetext" href="http://www.freeipa.org/page/V4/Sub-CAs#VPN_authentication">http://www.freeipa.org/page/V4/Sub-CAs#VPN_authentication</a></p>
<p>* <a class="moz-txt-link-freetext" href="http://www.freeipa.org/page/User_certificate_use_cases">http://www.freeipa.org/page/User_certificate_use_cases</a></p>
<p><br>
</p>
<p>Regards,</p>
<p>Phil<br>
</p>
</body>
</html>