Hello together, I wanted to ask what the status of this project, and as well of it's ECC support is. In Germany it's not even possible to get the RedHat supported version of this anymore, and it seems that most ECC- related issues (e.g. https://pagure.io/dogtagpki/issue/2574 isn't only a 'shared instance issue', and I get the same issue on OSCP: "com.netscape.certsrv.base.PKIException: Error in setting certificate names and key sizes: java.lang.ClassCastException: org.mozilla.jss.pkcs11.PK11ECPublicKey cannot be cast to java.security.interfaces.RSAPublicKey") are not even getting assigned.
I'd appreciate an honest opinion - does it make sense to build on dogtag/RHCS at all, or is it wiser to look for something else, with my issues as above?
Thanks a lot in advance, Chris
Metadata Update from @mharmsen: - Custom field component adjusted to General - Custom field feature adjusted to '' - Custom field origin adjusted to Community - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Hi, I have not tried "shared tomcat instances" so I cannot speak for that. However, I have very recent success in installing ECC CA/KRA/OCSP as separate Tomcat instances (all on the same box). The ECC CA is able to handle ECC CRMF requests successfully. Keys appear to be archived and recovered successfully to and from the ECC KRA as well. I did not have a chance to test out the ECC OCSP server yet, but it did install without a glitch.
If there is no compelling reason why "shared instance" has to be deployed, would you like to try installing them as separate instances?
Hi and thanks for your comment, but I actually decided that it won't make sense for me to go with this Software, for the reasons of activity, support and availability...
Cheers, Chris
Since separate tomcat instances work, and shared tomcat instance already has a ticket for, I'm closing this bug.
Metadata Update from @cfu: - Issue close_status updated to: duplicate - Issue status updated to: Closed (was: Open)
Metadata Update from @vakwetu: - Issue priority set to: major - Issue set to the milestone: 10.5 (was: 0.0 NEEDS_TRIAGE)
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5.0 (was: 10.5)
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/2894
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.