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

Question

Question

Repository users spontaneously change to be disabled

asked on March 23, 2023 Show version history

Hello LF Community,

I have an anomaly occurring where random repository users will switch from active to disabled:


We're not sure exactly when it occurs since we only find out when a users reports they can't access a doc. 


Has anyone else seen this before?

 

My mind goes to if Workflow could be doing this, but this post mentions that it is not possible unless using a  script. 

I have spent many hours digging through Audit Trail. One interesting I found is that when the admin goes in to change the user back to and active statues, that registers in Audit Trail as a change to the trustee name. Here is an example:

As you can see, there is no change. The names are the same. 

Can anyone at Laserfiche confirm this is expected behavior?

Posting here is the first step in trying to find a solution. Next step is submitting a support ticket to Laserfiche and likely uploading some SQL logs :)

What about failed attempts? At what point does the account become disabled after X number of failed logins? Could that be a possibility?

I also wonder if there is a location in the database where I might be able to see any info on when and who/what changed a user to disabled?? I know it's a long shot..


We are using Rio LFS version 11.0.0.206. The issue began after upgrading to 11. 

 

Thanks so much for your time. 


@████████

0 0

Answer

APPROVED ANSWER SELECTED ANSWER
replied on March 24, 2023

Hi Chris, Failed login attempts can lock the account if your Repository Options Settings are configured to do so (See below). You can check in the Laserfiche Administration Console.

Also, LF will only allow a user account to have 3 or 4 sessions running at a time. If they attempt to open an addition session beyond that, it could disable the account as well.

5 0
replied on March 24, 2023

Great tip Steve, thanks! I am inquiring now if these accounts could sit dormant for 30 days which would lock them out. 

0 0
replied on March 24, 2023

So it turns out it was that these users were locking out after 30 days. Thanks for the assist Steve!

1 0

Replies

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

Sign in to reply to this post.