Question

Demonstrating LF Audit Trail

Audit Trail Laserfiche

Updated October 6, 2015

asked on June 29, 2015

As a VAR we have an issue with demonstrating Audit Trail away from our office. We aren't able to log in since Audit Trail can't verify our credentials against our Active Directory. Other applications work just fine and seem to just use our cached windows credentials to allow us to use Windows Authentication in the LF Client, Web Access, even apps using the toolkit. The only issue we run into is that Audit Trail won't allow us to log in when we aren't connected to our network.

On that same note, it seems the other LF apps are slow to log in if I am on a network. Seems like it is waiting for the AD server request to time out before using cached credentials. However, if I have all networks turned off "airplane mode" on my Windows 8.1 laptop it is really snappy. Any way to get LF to ALWAYS use the cached credentials rather than wait to time out looking for the AD server?

0 0

Replies

replied on June 30, 2015

Hi Jason,

Sounds like it's slow looking for the DNS name resolution. Try disabling the DNS lookup and see if that makes it any faster.

https://support.laserfiche.com/KB/1012934

Hope this helps!

0 0

replied on October 5, 2015

Finally got around to having time to try this. When I am not connected to any network, I get the error below. I have not tried logging in to my laptop as a local user, not sure if that would work but the config allows me to add my local user as an authorized user of Audit Trail.

As a reminder. All other products that use windows authentication work. LF Client, Web Access, our own products that authenticate off LF via Windows Auth. Just Audit Trail fails.

About | Start Over | Configuration

The trust relationship between this workstation and the primary domain failed.

There may be additional information in the event viewer.

0 0

replied on October 6, 2015

So it all works fine when you are connected to a network?

0 0

replied on October 6, 2015

No, audit only works with connected to our domain. If I am not connected to our domain via VPN or directly, it can't see our domain controller to authenticate me.

All other apps that use windows authentication work fine regardless of network connection. They simply used cached credentials (just like windows does) rather than requiring a connection to the actual domain controller.

0 0

You are not allowed to follow up in this post.

Question

Question

Demonstrating LF Audit Trail

Replies

Sign in to reply to this post.