New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow CA to process pre-signed CMC revocation non-signing cert requests #2739
Comments
Comment from mharmsen (@mharmsen) at 2017-03-20 12:19:44 Metadata Update from @mharmsen:
|
1 similar comment
Comment from mharmsen (@mharmsen) at 2017-03-20 12:19:44 Metadata Update from @mharmsen:
|
Comment from mharmsen (@mharmsen) at 2017-03-20 12:22:10 Metadata Update from @mharmsen:
|
Comment from mharmsen (@mharmsen) at 2017-03-20 12:28:33 Metadata Update from @mharmsen:
|
Comment from cfu (@cfu) at 2017-05-30 17:13:50 Metadata Update from @cfu:
|
Comment from cfu (@cfu) at 2017-06-08 21:17:03 commit 698192f |
Comment from cfu (@cfu) at 2017-06-08 21:17:04 Metadata Update from @cfu:
|
Comment from mharmsen (@mharmsen) at 2017-06-09 14:41:06 Metadata Update from @mharmsen:
|
Comment from mharmsen (@mharmsen) at 2017-06-09 14:43:56 Metadata Update from @mharmsen:
|
This issue was migrated from Pagure Issue #2619. Originally filed by mharmsen (@mharmsen) on 2017-03-20 12:19:43:
This task should allow both signing and non-signing cmc revocation cert
requests to be signed by a previously-issued signing certificate of the same
subjectDN.
The server should be able to
This task might be companioning task for
https://pagure.io/dogtagpki/issue/2617 and
https://pagure.io/dogtagpki/issue/2618
(same assignee is recommended)
The text was updated successfully, but these errors were encountered: