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

Question

Question

Laserfiche Directory User Forms status Invalid

asked on February 26, 2018

Good day all,

 

On our RIO system, we have created 2 new users as Laserfiche Directory Users and allocated them Full Named User licences. 

 

The users can access the Repository and the Forms server but their status is listed as Invalid in Forms. This means I cannot assign Tasks to them. In addition, the email details are empty despite this information being entered in the Directory Server. 

 

Any suggestions? 

 

Regards

Ian

0 0

Replies

replied on February 26, 2018

Hi Ian,

Are you using LFDS? If so, the user need to be added to a group which is a whitelist group configured on Formsconfig page. After that, you can do manual synchronization and the users should show up in the list.

0 0
replied on February 26, 2018

Good day Rui,

 

Thank you for the reply. We are using LFDS but not to authenticate to Forms. We use the repository access. 

 

I have created a group on LFDS and added these users. 

 

Then on the repository, I have added the group as a Directory Server with access. 

 

The users show up in Forms and can log in, just status is invalid 

0 0
replied on February 27, 2018

In Forms 10.3.0 we have fixes to allow users/groups added to Laserfiche Directory Accounts to be synchronized, but we don't synchronize users belonging to group when only group is added. I was able to reproduce the issue that user can login but shows as invalid if only group is added. This seems to be a bug but we need to check how this should be handled, sorry for the inconvenience.

If you are on Forms 10.3.0, can you add the users to Laserfiche Directory Accounts directly as a workaround?

For Forms before 10.3.0, the fix is not there so if you are on Forms 10.2.1 accounts could not be synchronized at all.

0 0
replied on March 7, 2018

Thanks for the feedback

I'll do the work around

 

Regards

Ian 

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

Sign in to reply to this post.