https://bugzilla.redhat.com/show_bug.cgi?id=807073 - Config wizard: adminpanel fails at nsIDOMCrypto.generateCRMFRequest when CS instance name (hence the DN) is long [[BR]] [[BR]]
When installing with a CA instance with a long name such as "pki-ca-nethsm-nss-ecc-fips1E1SELinux03262012a" the config wizard fails with the following error in the Firefox Error Console at the adminpanel:
Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMCrypto.generateCRMFRequest]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: https://<hostname>:9965/ca/admin/console/config/wizard :: performPanel :: line 211" data: no]
Workaround is to have a shorter name. We should at least release note this. I don't have time to find out exactly how long is too long. [[BR]] [[BR]]
For future reference, I printed out the DN that suspected of causing generateCRMFRequest() to break:
dn=cn=CA Administrator of Instance pki-ca-nethsm-nss-ecc-fips1E1SELinux03262012a1,uid=admin,e=xxx@redhat.com,o=DsdevSjcRedhat Domain 1
[[BR]] [[BR]]
I found the cause.
RFC 3280 defines an upper bound of 64 bytes for the CN attribute.
http://tools.ietf.org/html/rfc3280#appendix-A.1 -- Upper Bounds ub-common-name INTEGER ::= 64
http://mxr.mozilla.org/mozilla-central/source/security/nss/lib/certdb/alg1485.c#58
Resolving as not-a-bug. [[BR]] [[BR]]
Re-opening against Certificate System. We should perform some upper bounds checking before calling generateCRMF().
Metadata Update from @awnuk: - Issue set to the milestone: UNTRIAGED
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/1209
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.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.