#2574 KRA ECC installation failed with shared tomcat
Closed: migrated 3 years ago by dmoluguw. Opened 7 years ago by gkapoor.

KRA ECC installation with shared tomcat failed.CA installation went fine
Error :

java.lang.ClassCastException: org.mozilla.jss.pkcs11.PK11ECPublicKey cannot be
cast to java.security.interfaces.RSAPublicKey

Looks to be broken functionality (commit
:b834efbaa8c929c10cf00252b71ebc29e2f10456)

Steps to Reproduce:

Configure KRA with ECC on shared tomcat.

Actual results:

java.lang.ClassCastException: org.mozilla.jss.pkcs11.PK11ECPublicKey cannot be
cast to java.security.interfaces.RSAPublicKey

Expected results:

KRA installation should work

Additional info:

Created  debug_logs attachment in corresponding bug.

Configuration file :
-------------------
[DEFAULT]
pki_admin_password=Secret123
#pki_admin_keysize=nistp384
#pki_admin_key_type=ecc
pki_client_pkcs12_password=Secret123
pki_ds_password=Secret123
pki_security_domain_password=Secret123
pki_client_database_password=Secret123

[KRA]
pki_import_admin_cert=False
pki_storage_key_type=rsa
pki_storage_key_size=2048
pki_storage_key_algorithm=SHA256withRSA
pki_storage_signing_algorithm=SHA256withRSA
pki_transport_key_type=rsa
pki_transport_key_size=2048
pki_transport_key_algorithm=SHA256withRSA
pki_transport_signing_algorithm=SHA256withRSA
pki_ssl_server_key_type=ecc
pki_ssl_server_key_size=nistp384
pki_ssl_server_key_algorithm=SHA384withEC
pki_ssl_server_signing_algorithm=SHA384withEC
pki_subsystem_key_type=ecc
pki_subsystem_key_size=nistp384
pki_subsystem_key_algorithm=SHA384withEC
pki_subsystem_signing_algorithm=SHA384withEC

Metadata Update from @gkapoor:
- Issue set to the milestone: 0.0 NEEDS_TRIAGE

7 years ago

Metadata Update from @mharmsen:
- Custom field feature adjusted to ''
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field version adjusted to ''
- Issue close_status updated to: None
- Issue priority set to: 3
- Issue set to the milestone: 10.4 (was: 0.0 NEEDS_TRIAGE)

7 years ago

Per CS/DS Meeting of August 7, 2017, it was determined to move this issue from 10.4 ==> FUTURE.

Metadata Update from @mharmsen:
- Issue set to the milestone: FUTURE (was: 10.4)

6 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/2694

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