Skip to content
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

Closed
pki-bot opened this issue Oct 3, 2020 · 9 comments
Closed
Milestone

Comments

@pki-bot
Copy link

pki-bot commented Oct 3, 2020

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

  1. verify the signature
  2. match the signer with the revocation request subject
  3. approve or deny or pending

This task might be companioning task for
https://pagure.io/dogtagpki/issue/2617 and
https://pagure.io/dogtagpki/issue/2618
(same assignee is recommended)

@pki-bot pki-bot added this to the 10.4.8 milestone Oct 3, 2020
@pki-bot pki-bot closed this as completed Oct 3, 2020
@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from mharmsen (@mharmsen) at 2017-03-20 12:19:44

Metadata Update from @mharmsen:

1 similar comment
@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from mharmsen (@mharmsen) at 2017-03-20 12:19:44

Metadata Update from @mharmsen:

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from mharmsen (@mharmsen) at 2017-03-20 12:22:10

Metadata Update from @mharmsen:

  • Custom field component adjusted to General
  • Custom field feature adjusted to ''
  • Custom field origin adjusted to Community
  • Custom field proposedmilestone adjusted to ''
  • Custom field proposedpriority adjusted to ''
  • Custom field reviewer adjusted to ''
  • Custom field type adjusted to defect
  • Custom field version adjusted to ''
  • Issue priority set to: 2

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from mharmsen (@mharmsen) at 2017-03-20 12:28:33

Metadata Update from @mharmsen:

  • Custom field component adjusted to CMC (was: General)
  • Custom field origin adjusted to RHCust (was: Community)
  • Custom field type adjusted to enhancement (was: defect)

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from cfu (@cfu) at 2017-05-30 17:13:50

Metadata Update from @cfu:

  • Issue assigned to cfu

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from cfu (@cfu) at 2017-06-08 21:17:03

commit 698192f
Author: Christina Fu cfu@redhat.com
Date: Tue May 30 14:12:06 2017 -0700

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from cfu (@cfu) at 2017-06-08 21:17:04

Metadata Update from @cfu:

  • Issue close_status updated to: fixed
  • Issue status updated to: Closed (was: Open)

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from mharmsen (@mharmsen) at 2017-06-09 14:41:06

Metadata Update from @mharmsen:

  • Issue set to the milestone: 10.4.8 (was: 10.4)

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from mharmsen (@mharmsen) at 2017-06-09 14:43:56

Metadata Update from @mharmsen:

  • Issue priority set to: blocker (was: critical)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant