#3147 caDirUserCert on CA End-Entity Page not showing RSA algorithm option in drop down
Closed: migrated 3 years ago by dmoluguw. Opened 4 years ago by cipherboy.

Description of problem:

caDirUserCert on CA End-Entity page not showing RSA algo. implementation as default selection of ECC in key parameters, as in result request is getting rejected, because 1024,2048 curve types for ECC

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

PKI Command-Line Interface 10.5.9-3.el7

Steps to Reproduce:

  1. I have created 'test' user and added in ldap directory server.

  2. I have enabled the "UidPwdDirAuth" plugin through pkiconsole.

  3. Go to End-Entity page and submit request to 'Directory-Authenticated User Dual-Use Certificate Enrollment' profile (caDirUserCert)

Parameters: LDAP uid="test",LDAP password="redhat"

so it is not showing RSA algorithm in drop down but it takes RSA key length as a ECC curve parameter

Actual results:

Sorry, your request has been rejected. The reason is "Request 25 Rejected - Key Parameters 1024,2048,3072,4096 Not Matched"

Your request ID is 25.

Expected results:

It should generate the certificate.

Additional info:


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=1610718
- 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/3264

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