dogtagpki

#2692 caUserCert profile couldn't parse multiple CN's while testing BZ 1305993
Closed: wontfix Opened by mharmsen.

Closed: wontfix
Reopen Issue

While testing multiple CN's for profile caUserCert looks like the handling is
not proper.

In caUserCert , if we specify multiple CN's it taken as because of which no SAN
extension is getting added.

Subject: UID=testuser,CN=testing.example.com\,1.example.com

So for CaUserCert, multiple CN are not taken properly.CSR construction is not
as expected.

With CaServerCert:

        Subject: CN=test.example.com,CN=1.example.com
        Extensions:
            Identifier: Authority Key Identifier - 2.5.29.35
                Critical: no
                Key Identifier:
                    23:C1:52:30:49:97:F1:33:3E:6E:97:96:1D:86:59:1F:
                    3F:E6:E2:A4
            Identifier: Subject Alternative Name - 2.5.29.17
                Critical: no
                Value:
                    DNSName: test.example.com

Steps to Reproduce:

1. Disable the CauserCert profile.
2. Add the below mentioned fields in the caUserCert.
<fields to add in profile caUserCert>
policyset.userCertSet.11.constraint.class_id=noConstraintImpl
policyset.userCertSet.11.constraint.name=No Constraint
policyset.userCertSet.11.default.class_id=commonNameToSANDefaultImpl
policyset.userCertSet.11.default.name=Copy Common Name to Subject Alternative
Namepolicyset.userCertSet.8.constraint.class_id=noConstraintImpl
policyset.userCertSet.8.constraint.name=No Constraint
policyset.userCertSet.8.default.class_id=subjectAltNameExtDefaultImpl
policyset.userCertSet.8.default.name=Subject Alt Name Constraint
policyset.userCertSet.8.default.params.subjAltExtGNEnable_0=true
policyset.userCertSet.8.default.params.subjAltExtGNEnable_1=true
policyset.userCertSet.8.default.params.subjAltExtGNEnable_2=true
policyset.userCertSet.8.default.params.subjAltExtPattern_0=$request.requestor_e
mail$
policyset.userCertSet.8.default.params.subjAltExtPattern_1=pki1.example.com
policyset.userCertSet.8.default.params.subjAltExtPattern_2=$request.uid$
policyset.userCertSet.8.default.params.subjAltExtType_0=RFC822Name
policyset.userCertSet.8.default.params.subjAltExtType_1=DNSName
policyset.userCertSet.8.default.params.subjAltExtType_2=DNSName
policyset.userCertSet.8.default.params.subjAltNameExtCritical=false
policyset.userCertSet.8.default.params.subjAltNameNumGNs=5
</filds to add in caUserCert>
policyset.userCertSet.list=1,10,2,3,4,5,6,7,8,9,11
3.Enable the profile.

Actual results:

most specific CN is not getting pick in case of multiple CN's.Same test case
works in caServerCert.

Expected results:

CaUserCert when have multiple CN's , it should be able to pick left most CN in
SAN extensions.

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 rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1451188
- Custom field type adjusted to defect
- Custom field version adjusted to ''

Metadata Update from @mharmsen:
- Issue assigned to mharmsen

Metadata Update from @mharmsen:
- Issue assigned to ftweedal (was: mharmsen)

Metadata Update from @mharmsen:
- Issue priority set to: critical

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5 (was: 10.4)

Metadata Update from @ftweedal:
- Assignee reset

Metadata Update from @mharmsen:
- Issue priority set to: major (was: critical)
- Issue set to the milestone: FUTURE (was: 10.5)

Per 10.5.x/10.6 Triage:

ftweedal: obscure use case. close WONTFIX

Metadata Update from @mharmsen:
- Issue close_status updated to: wontfix
- Issue set to the milestone: 10.5.7 (was: FUTURE)
- 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/2812

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
None
None
None
None
Normal
defect
General
''
''
Community
''
''
''
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.