dogtagpki

#2942 Usability Improvements for cmc.popLinkWitnessRequired=true
Closed: migrated by dmoluguw. Opened by mharmsen.

Closed: migrated
Reopen Issue

Use Case:

if we set cmc.popLinkWitnessRequired=true in CS.cfg, So while signing ca cmc cert will it look for poplinkwitness?

If we want poplinkwitness for some profiles and for some we don't need that how we can do that?

example: we don't wanted to give poplinkwitness for CA signing using caCMCcacert but we want for other profiles.

Setting this flag in profile gives user more flexibility.

in case of casigning cert it does look for poplinkwitness, if it is set in CS.cfg.So to make it work i have to set cmc.popLinkWitnessRequired=false and then it signs the certificate

Steps to Reproduce:

1.Set cmc.popLinkWitnessRequired=true
2.try to sign ca signing certificate using http://pki.fedoraproject.org/wiki/Issuing_CA_Signing_Certificate_with_CMC
3. HttpClient will fail with 
Number of controls is 1
Control #0: CMCStatusInfoV2
   OID: {1 3 6 1 5 5 7 7 25}
   BodyList: 0 
   Status String: POP Link Witness Verification Failed:missing needed randomSeed or identification for popLinkWitness(V2)
   OtherInfo type: FAIL
     failInfo=bad request
ERROR: CMC status for [0]: failed

Actual results:

It doesn't work right now.So if we need to sign such certs we need to first set cmc.popLinkWitnessRequired=false

Expected results:

poplinkwitness is not required for agent signed certificates like ca signing.

Metadata Update from @mharmsen:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None
- Issue priority set to: major
- Issue set to the milestone: 10.5

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1545872

Per 10.5.x/10.6 Triage: 10.5.x

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/3060

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
Normal
None
None
None
None
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.