Steps to Reproduce:
1. Setup CA and KRA with ECC 2. Add the following parameters to KRAs CS.cfg kra.allowEncDecrypt.archival=true kra.allowEncDecrypt.recovery=true kra.legacyPKCS12=false 3. request a client certificate using the following command: pki -v -d /tmp/nssdb/ -c SECret.123 client-cert-request CN=foo1 --profile caSigningUserCert --type crmf --algorithm ec --curve nistp256
Here the caSigningUserCert is used because caSigningECUserCert is not enabled by default. I have used the workaround where first stop the CA, put the contents of caSigningECUserCert into caSigningUserCert since the system does not let me enable caSigningECUserCert and then restart CA
Actual results:
The command fails with NullPointerException
Expected results:
The client-cert-request should succeed
Additional info:
By default the caSigningECUserCert profile should be enabled for ECC installation to be used for CRMF requests
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 rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1590233 - Custom field type adjusted to None - Custom field version adjusted to None
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/3182
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)