Replies: 2 comments 4 replies
-
Hello Jan, I can not answer directly for the LOG_AUDIT_TO_DB ENV, maybe somebody else knows more of its function in the container packaging and can jump in? Regarding the We are discussing if we should change the container packaging to configure the signserver.ear during startup so that all properties are read from conf/signserver_deploy.properties and conf/cesecore.properties etc., as the current way also removes some other features. The other solution of adding support for external configuration is tracked in DSS-1107 (Note the link might not be accessible currently due to system upgrade but I am including it here for reference for when it comes back). |
Beta Was this translation helpful? Give feedback.
-
Hello, Thanks |
Beta Was this translation helpful? Give feedback.
-
Hello,
we are investigating docker based deployment for production use and thus would like to enable audit logging.
We realized the ENV variable LOG_AUDIT_TO_DB, but that does not seem to have any impact, is that correct?
We also tried editing cesescore.properties but it looks like changes in this file are not read, as allow.external-dynamic.configuration seems to be off in the container image?
The default cesescore.properties seems to look like this:
\# Allow override of CESeCore config files from /etc/cesecore/conf/
\# FIXME: DSS-2377
\# allow.external-dynamic.configuration=true
Are we missing something?
Thank you very much for any hints and suggestions in advance!
Jan
Beta Was this translation helpful? Give feedback.
All reactions