Mike Kushner

Hi Dan, Yeah, the documentation is sadly hosted on our internal Confluence servers, and we haven't figured a quick and dirty way of exposing our Confluence for external builds I absolutely see your issue, and we'll take it into account the next time we're discussing community support. Cheers, Mike

Hi Sebastien, Since you're an Enterprise user, I suggest you contact our support team - assistance here on Sourceforge is primarily for the Community and is done in our free time, so you're likely to get a quicker response there. Cheers, Mike

Hi Amy, Run the command with the --help flag, and you'll get a full man page. Cheers, Mike

Hi Paskal, If you want to branch EJBCA, I'm afraid you're on your own =) If not, then you're welcome to drop us a line for a quote about a subscription to Enterprise. Cheers, Mike

Hi, No - CLI Support as well as the WS API are still there, it's merely CT configuration that is not implemented in the CLI. Cheers, Mike

Hi Paskal, EJBCA currently only supports CT configuration through the UI, and CT is indeed an Enterprise feature. Cheers, Mike

Hi, I presume that you mean the EJBCA RA here? It's not at all a bad idea per-say, you just need to be aware of the fact that it exposes the RA to anybody who can access it on the network - posting it publicly on the internet mostly risks getting DOSed with fradulent requests, but there's no inherent security risk in doing so. Cheers, Mike

Prerelease – Get EJBCA Community 7.4.0 before its official release