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

Question

Question

Adding LFDS users to a repository

asked on August 9, 2016

Hi - We register our users within LFDS (v10) via Windows AD accounts.  When we wish to grant these global users access to a specific repository, it becomes a bit confusing for me.  Do we simply add a new user in the Admin Console by specifying New Windows Account User?  I would have thought there was a selection to pick from the existing LFDS user pool, rather than search the full AD database - it seems like a disconnect.

Also, if we are adding "global" users from LFDS, must I first allocate "Repository Named User Licenses"?  I was led to believe that parameter was only for licenses created in and restricted to that repository.  When we licensed the repository, we kept that number very low - expecting that all users would be managed in LFDS and then granted access to the specific repositories required.

Thanks in advance for the info.  I recognize this is a basic subject, but I can't seem to find a clear answer in the Admin Guide or other posts.

Thanks again, .... Steven.

1 0

Replies

replied on August 10, 2016

Hi James,

Thanks for your thorough response.  Unfortunately, it seems like the answers to #1 and #2 conflict with each other, unless I misunderstand you (which is likely!).  So, if my plan calls for me to add users in LFDS and then trust them to a repository (so that I can add a user to >1 repository without consuming >1 license), how do I do the second step in the Admin Console, by (i) adding a Windows Account user, or (ii) adding a Laserfiche Directory user?

Currently, I am able to add Windows Account users, but I cannot add Laserfiche Directory users.  When I try to add, I find that the "Locations" field is not populated, and I can't seem to change that.  Is that a field that should auto-populate via communication with LFDS?  Or, is that controlled by a config setting?

Thanks much, ..... Steven.

 

1 0
replied on August 10, 2016

Hi Steven, it might be the unfortunate choice of terminology. In the Admin Console, "Laserfiche Directory Account" refers to the "Laserfiche users" added in LFDS, the ones which show up with an orange circle in the list of Accounts in LFDS. When adding a new Laserfiche Directory Account, the "from this location" field should be filled with "lfds" and read-only. If this is blank, there may be an issue.

0 0
replied on August 10, 2016

So, by "Laserfiche users" in LFDS, do you mean users created in LFDS, not linked to an AD account?  If so, we do not have any of those (yet).  All of our users (so far) originate from an AD pool, and are created in LFDS as "Windows Active Directory Users", the ones with the blue dot.  Knowing that, how do I add them into a repository without consuming additional licenses beyond the one they already took in LFDS?

If the answer is to simply add a "New Windows Account User" in the Admin Console within the repository, that's OK, I can do that.  But, they come in with "False" attribute as "Named User", and when you open the Properties there is no toggle to go "Full", as you would see if you created a "New Repository User".

Is that behavior what you would expect to see?

And BTW, the Locations field for "Laserfiche Directory Users" is blank.

Thanks, .... Steven.

0 0
replied on August 10, 2016

In LFDS you can verify that they have a Full license assigned? If so, there may be a communication issue between LFS and LFDS. Try restarting the Laserfiche Server and see if the license status of these AD users updates to a full license. At this point I would also recommend you reach out to your reseller for additional troubleshooting.

0 0
replied on August 10, 2016

Thank you, James, for all the info.  Yes, they are Full users in LFDS.  I will reach out to our VAR for support on this issue.

At the risk of beating this dead horse, can you answer the above question, repeated here - if we have global users created in LFDS as Windows AD users, how do I add them to individual repositories?  Is it by adding "New Windows Account Users" from within the Admin Console (as opposed to "New Laserfiche Directory User")?

Thanks again, ..... Steven.

0 0
replied on August 10, 2016

No worries, Steven. If they are Windows AD users licensed in LFDS, they should be added using "New Windows Account Users" in the Admin Console.

0 0
replied on August 10, 2016

Thanks so much, James - really appreciate the help and info!

0 0
replied on April 2

Please update your link for this solution.

replied on April 4

Hello,

I may be doing this wrong but I didn't have to grant access to users in the repository through "New Windows Account Users" from the Admin Console. I granted the everyone group "trusted:allow" access to the repository. Since all users (AD or LF users) are part of the "everyone" group, I just granted access to that group through the repository, with limited rights of course. They then inherited access rights through the "everyone" group and was allowed access to repository. Should I not be doing it this way?

 

Thanks,

Mui

0 0
replied on August 9, 2016 Show version history

Hi Steven,

You can consult the Laserfiche Rio Deployment Guide; I think something along these lines is what you were searching for.

To answer your questions, though:

  1. Do we simply add a new user in the Admin Console by specifying New Windows Account User? Yes; in LFDS, the license is allocated to the Windows user but in LFS (through the Admin Console) access to the repositories is granted. This is because the same Admin Console is used for Rio (which has LFDS) and non-Rio (which don't) versions of the Laserfiche suite, so it cannot only poll the LFDS user pool. Also this avoids the situation where a license might have been allocated in LFDS to a user which is no longer in Active Directory, while LFDS has not yet been synced with AD.
  2. If we are adding "global" users from LFDS, must I first allocate "Repository Named User Licenses"? No; adding "global" Laserfiche users from LFDS is achieved through the "New Laserfiche Directory Account" node in the Admin Console and works similarly to adding a new Windows or LDAP user; the licensing is handled by LFDS, but in the Admin Console you will trust these users with access to the repository. Your understanding of the Repository Named Users is correct.

Hope this helps!

Edits: minor phrasing and stray spaces

0 0
replied on April 2

Please update your link for this solution.

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

Sign in to reply to this post.