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

Question

Question

LFDS User Licensing

asked on February 1, 2016

Hi,

Quick question about the new users in the Directory Server.

Is it possible to setup Standard Laserfiche Users in LFDS for repositories that cannot see the Directory Server (i.e on a different domain) or will there need to be a trust?

If no trust is needed, when setting up these accounts and browsing to them via - where is the information for the Directory Server stored?

Thanks,

Dom

0 0

Answer

SELECTED ANSWER
replied on February 5, 2016

To log with LFDS, the Laserfiche Server needs to be able to contact LFDS. In a Rio/Laserfiche Directory Setup, the Laserfiche Server needs to be able to contact LFDS periodically to validate its license.

1 0

Replies

replied on February 5, 2016

Hi Dominic,

The phrasing is throwing me off a little, but if you mean is it possible to setup Laserfiche users who cannot see the Directory Server than yes it is. That would be the case for the majority of users (i.e. not adminstrators).

However, if you mean can you set up Laserfiche users in a scenario in which it is the repository that cannot see the Directory server than the answer would be no.

Best,
Kevin

2 0
replied on February 8, 2016

Hi Kevin,

Sorry for my poor phrasing, you answered my question in the second scenario you mentioned. I wasn't too sure on how these accounts were distributed - whether (as Miruna stated) the repository had to be in contact with LFDS at all times for periodic licensing. 

Just to clarify my second question - after setting up these 'Laserfiche Users', should I be able to browse them in the Administration Console under Laserfiche Directory Accounts? Does this method of browsing accounts use the LFDS host name from the license file on the server (if licensed using that method)?

Thanks

0 0
replied on February 8, 2016

Yes, the LFDS users will be available in the LF Admin Console. And yes, the Laserfiche Server establishes the location of LFDS based on its license.

1 0
replied on February 8, 2016

Not a problem at all. I just wanted to be sure I was understanding you correctly. Hopefully things are a little more clear now!

1 0
replied on May 25, 2016

I'm assuming a typical install would see host names that resolve on a local network, but I have an scenario where the Laserfiche Server needs to know the FQDN host name of the Laserfiche Directory Server.  I cannot find any reference of where to set this except in the CONFIG file "UserSettings" in C:\ProgramData\Laserfiche\LFDS.  However, changing this prevents the web LFDS site from working properly.

Is there a proper way to embed the FQDN in the setup so that the license file will contain this so that the Laserfiche Server can communicate with LFDS?  My next work around will be creating an entry in a host file.

In my scenario the LFDS and LFS are not members of same network/domain/active directory.

0 0
replied on May 26, 2016

Hi Lewayne,

This was the problem we were experiencing whereby the the license file for the LFS contained the hostname of the LFDS that could not be resolved externally - so it was unable to communicate.

I believe in our scenario we just created an entry in the hosts file to bind the hostname that is in the LFS license file to the external IP of the LFDS. 

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

Sign in to reply to this post.