You are viewing limited content. For full access, please sign in.

Question

Question

How does LF Server log audit events?

asked on January 23, 2019

Our organization's security policy only allows us to use TLS 1.2. Since Audit Trail reporting currently doesn't work with TLS 1.2, we are considering disabling it until needed (we rarely use it). Since the events are logged by the Laserfiche Server to a file I thought we could just let it log events and then enable TLS 1.0 when we need to run reports. However, it doesn't work. If I disable the Audit Trail reporting service and the SQL Server events continue to be logged. Once I disable TLS 1.0 events stopped being logged.

How are audit events logged? Is it possible to configure the server to log audit events without requiring TLS 1.2? We are running Laserfiche Avante 10.3.1.

Thanks.

0 0

Replies

replied on January 23, 2019

The server logs to flat files on disk which Audit Trail Reporting then processes into a database. Disabling the reporter because of the TLS issue will not stop the server from logging to the log files. It will only stop the reporter from loading them into the database. When you re-enable it, it will catch up on processing the existing logs for the time range specified.

We are planning on releasing a fix for the configuration issue in the next week or so.

0 0
replied on January 24, 2019

Yes, when I turn off the reporter it still logs the events to the file. However, when I turn off the reporter *and* only enable TLS 1.2, it stops logging to the file.  What mechanism is used to write to the file? I had assumed it wrote to it directly. Maybe its using some sort of web service?

0 0
replied on January 24, 2019

Please contact your reseller and open a case with Tech Support so we can investigate this further.

0 0
replied on January 24, 2019

Can you open a case directly? Our reseller won't help us with this since its part of an upgrade we are performing ourselves.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.