#3160 Curl request with the certificate is not working for KRA
Closed: migrated 3 years ago by dmoluguw. Opened 4 years ago by cipherboy.

Description of problem:
Curl tool not able to create request with the certificate.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create kraadmin user. add it to the 'Administrator' group.
2. Add the certificate to the user.
3. Get the certificate and convert it to pem file.
4. curl -kv -L -E ./kraadmin.pem "https://pki1.example.com:21443/kra/server?RS_ID=serverCert&OP_TYPE=OP_READ&subjectName=&certType=serverCert&OP_SCOPE=subjectName"

Actual results:

# curl -kv -L -E ./kraadmin.pem "https://pki1.example.com:21443/kra/server?RS_ID=serverCert&OP_TYPE=OP_READ&subjectName=&certType=serverCert&OP_SCOPE=subjectName"
* About to connect() to pki1.example.com port 21443 (#0)
*   Trying 10.19.34.103...
* Connected to pki1.example.com (10.19.34.103) port 21443 (#0)
* Initializing NSS with certpath: sql:/opt/pki/certdb
* unable to load client key: -8178 (SEC_ERROR_BAD_KEY)
* NSS error -8178 (SEC_ERROR_BAD_KEY)
* Peer's public key is invalid.
* Closing connection 0
curl: (58) unable to load client key: -8178 (SEC_ERROR_BAD_KEY)
[root@auto-hv-01-guest01 ~]#

Expected results:
It should be successful.

Additional info:

export SSL_DIR=/opt/pki/certdb

Metadata Update from @cipherboy:
- 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=1549044
- Custom field type adjusted to None
- Custom field version adjusted to None

4 years ago

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

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 Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata