You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When deploying the EJBCA container to openshift the default managementCA keystore is corrupted.
I believe this is the cause:
ERROR [org.ejbca.core.ejb.StartupSingletonBean] (ServerService Thread Pool -- 106) BouncyCastle is not loaded by an EJBCA classloader, version conflict is likely: org.bouncycastle.jcajce.provider.asymmetric.x509.X509CertificateObject:"
[](url)
Hi, the issue may not be directly related to the Bitnami container image/Helm chart, but rather to how the application is being utilized, configured in your specific environment, or tied to a particular scenario that is not easy to reproduce on our side.
If you think that's not the case and want to contribute a solution, we'd like to invite you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.
Your contribution will greatly benefit the community. Please feel free to contact us if you have any questions or need assistance.
Suppose you have any questions about the application, customizing its content, or technology and infrastructure usage. In that case, we highly recommend that you refer to the forums and user guides provided by the project responsible for the application or technology.
With that said, we'll keep this ticket open until the stale bot automatically closes it, in case someone from the community contributes valuable insights.
Name and Version
Bitnami/ejbca
What architecture are you using?
amd64
What steps will reproduce the bug?
When deploying the EJBCA container to openshift the default managementCA keystore is corrupted.
I believe this is the cause:
Are you using any custom parameters or values?
What is the expected behavior?
Keystore is generated for superadmin
What do you see instead?
Additional information
This problem causes the ManagementCA to not generate certificates
The text was updated successfully, but these errors were encountered: