Replies: 2 comments
-
How the container starts up, if it creates an initial ManagementCA or not is controlled by the environment variable TLS_SETUP_ENABLED. See https://hub.docker.com/r/keyfactor/ejbca-ce |
Beta Was this translation helpful? Give feedback.
0 replies
-
Yes indeed. I found that it is related to PROXY_HTTP_BIND variable. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I am trying to get EJBCA to work with containers.
I am using podman, witch is kind of the same of docker in terms of cmdlines.
I built 3 containers:
I am launching EJBCA, it connects to my external MySQL database correctly, creates all the tables needed.
The thing is:
Comparing to laucnhing EJBCA without an external Mysql DB, EJBCA automatically creates the Management CA and the superadmin role.
But when I use an external DB, the initialization of Management CA / SuperAdmin is not done.
So when I go to the front page, I cannot login / enroll the SuperAdmin User.
On EJBCA RA, I have this message:
The service is currently unavailable since no active CA is serving this RA.
What can I do, to make EJBCA initialize the first ManagementCA, and SuperAdmin account?
Beta Was this translation helpful? Give feedback.
All reactions