#3024 HSM support for HTTP NIO connector
Closed: fixed 5 years ago Opened 5 years ago by edewata.

In ticket #203, PKI switched to use HTTP NIO connector. With the current configuration, the SSL server certificate and key must be stored in a PKCS #12 file, they cannot be stored in HSM (although other system certs/keys can still be storen in HSM).

There are several options to support storing SSL server cert in HSM:

Option #1: Use JSS to provide a PKCS #11 keystore to HTTP NIO connector using keystoreType="pkcs11" (see https://tomcat.apache.org/tomcat-8.5-doc/ssl-howto.html#Configuration).

Option #2: Provide a JSS implementation for the HTTP NIO connector.


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 type adjusted to None
- Custom field version adjusted to None
- Issue set to the milestone: 0.0 NEEDS_TRIAGE

5 years ago

Metadata Update from @edewata:
- Issue priority set to: critical
- Issue set to the milestone: 10.6 (was: 0.0 NEEDS_TRIAGE)

5 years ago

Metadata Update from @edewata:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

5 years ago

Metadata Update from @edewata:
- Issue set to the milestone: 10.6.3 (was: 10.6)

5 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/3142

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.

Login to comment on this ticket.

Metadata