in an ECC setup, where ECC keys are generated on token, e.g. op.enroll.delegateISEtoken.keyGen.signing.alg=5 op.enroll.delegateISEtoken.keyGen.signing.keySize=256
running tpsclient would cause verifyProof() to fail on server side (TPS) You would see the following in the tps-debug: [2014-01-20 09:10:28] 868f770 CertEnroll::verifyProof - verify proof begins [2014-01-20 09:10:28] 868f770 CertEnroll::verifyProof - VFY_CreateContext() failed [2014-01-20 09:10:28] 868f770 CertEnroll::ParsePublicKeyBlob - verify proof failed [2014-01-20 09:10:28] 868f770 RA_Enroll_Processor::DoEnrollment - Failed to parse public key [2014-01-20 09:10:28] 868f770 RA_Enroll_Processor::GenerateCertificate - Got a status error from DoEnrollment: 7
Metadata Update from @cfu: - 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/1398
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.