<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Received verbal ack from jmagne. Did a demo to him as well.</p>
<p>pushed to master:</p>
<p>commit 3ff9de6a517d7fdcdee6c4a8c884eff052f8f824<br>
</p>
<br>
<div class="moz-cite-prefix">On 04/28/2017 06:06 PM, Christina Fu
wrote:<br>
</div>
<blockquote
cite="mid:d7189ca1-b4ce-fbf0-6f19-bb9de31b21c2@redhat.com"
type="cite"><a class="moz-txt-link-freetext" href="https://pagure.io/dogtagpki/issue/2617">https://pagure.io/dogtagpki/issue/2617</a>
<br>
<br>
This patch provides implementation that allows user-signed CMC
requests to be processed; The resulting certificate will bear the
same subjectDN as that of the signing cert;
<br>
<br>
The new uri to access is /ca/ee/ca/profileSubmitUserSignedCMCFull
where
<br>
<br>
the new profile is to be used: caFullCMCUserSignedCert.cfg which
utilizes
<br>
<br>
the new authentication plugin: CMCUserSignedAuth and
<br>
<br>
new profile default plugin: CMCUserSignedSubjectNameDefault and
<br>
<br>
new profile constraint plugin: CMCUserSignedSubjectNameConstraint
<br>
<br>
A separate ticket will be filed to handle Non-pre-signed user cmc
cert requests.
<br>
<br>
thanks,
<br>
<br>
Christina
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Pki-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Pki-devel@redhat.com">Pki-devel@redhat.com</a>
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/pki-devel">https://www.redhat.com/mailman/listinfo/pki-devel</a></pre>
</blockquote>
<br>
</body>
</html>