Problem:
When enrolling tokens for groups, one must first enroll a single token to obtain an encryption key to recover to the remaining tokens via certsToAdd.
Request:
Provide facility to do 'group token enrollment' - Agent provides list of users and tokens for enrollment - If no encryption certificate/key is provided via externalReg - Enroll first record - Obtain cert/key ID - Associate cert/key ID with group - Modify remaining records to add cert/key ID for externalReg - Recover cert/key to remaining tokens
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1254812 (Red Hat Certificate System)
Per CS/DS meeting of 11/02/2015: 10.3
Per cfu on IRC on 04/04/2016: 10.4
waiting on customer feedback
Metadata Update from @dsirrine: - Issue assigned to cfu - Issue set to the milestone: UNTRIAGED
Metadata Update from @mharmsen: - Custom field feature adjusted to '' - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field version adjusted to '' - Issue close_status updated to: None - Issue set to the milestone: 10.4 (was: UNTRIAGED)
Metadata Update from @mharmsen: - Issue priority set to: 2 (was: 3)
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5 (was: 10.4)
Metadata Update from @mharmsen: - Issue priority set to: major (was: critical)
[20171025] - Offline Triage ==> 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
Metadata Update from @mharmsen: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2219
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.