dogtagpki

#1386 CRMFPopClient fails when subject DN has Email
Closed: Invalid Opened by mharmsen.

Closed: Invalid
Reopen Issue

CRMFPopClient fails when Subject DN has Email specified ,

Example Command:

CRMFPopClient -d /tmp/tmp.pdS4Oa3k3k/nssdb -p redhat123 -o
/tmp/tmp.pdS4Oa3k3k/nssdb/2491-request.pem -n
"UID=FooBar,E=test@example.org,CN=?ric
T?ko,OU=Foo_Example_IT,O=FooBar.Org,C=US" -a rsa -l 2048 -u FooBar -r FooBar 1>
/tmp/tmp.pdS4Oa3k3k/nssdb/CRMFPopClient.out

Error:

ERROR: Unsupported attribute: E
Try 'CRMFPopClient --help' for more information
Version-Release number of selected component (if applicable):

Steps to Reproduce:

1. Install & configure pki-ca, pki-kra
2. create a NSS Db directory
3. Copy transport cert to the directory
4. Create CRMF request with subject DN having Email (Ex.:D=FooBar,E=FooBar@exam
ple.org,CN=FooBar,OU=Foo_Example_IT,O=FooBar.Org,C=US)

Actual results:

CRMFPopClient fails with Error:
ERROR: Unsupported attribute: E
Try 'CRMFPopClient --help' for more information.

Expected results:

CRMFPopClient should not fail

email in subject DN is legacy implementation that is not required to be supported by the CA. Closing this bug.

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.2.5

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

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
Tools
QE
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.