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

Question

Question

SignIx Intergration

asked on August 15, 2016

Good day,

 

We have recently begun implementing the new SignIx integration modules of Laserfiche. 

 

I have installed the web service on our public facing server while our Laserfiche server sits on a separate internal server. 

 

I would like Windows authentication to be the preferred method but I cannot find the server running on the server to configure the domain account to run. 

 

Should I go the route of Named User, I am also having trouble configuring the web.config file to allow this. 

 

These are the options I have but I am unsure of the formatting  to enter the full server name.

 

      * In the case that there are any repositories in your environment that share the same name (on different servers), 
        but you would like this service to connect to them with different authentication, 
        you can distinguish by including the full host name of the server (all lowercase) before the repository names, like this:
          <add key="LFUser-server.laserfiche.com-repositoryname" value="username" />
          <add key="LFUser-server.laserfiche.com-repositoryname" value="password" />
          <add key="LFUser-differentserver.laserfiche.com-repositoryname" value="username" />
          <add key="LFUser-differentserver.laserfiche.com-repositoryname" value="password" />
      
      * You can also use the machines' ip (v4) addresses instead of their names, if that's easier:
          <add key="LFUser-192.168.1.33-repositoryname" value="username" />
          <add key="LFUser-192.168.1.33-repositoryname" value="password" />
          <add key="LFUser-192.168.1.34-repositoryname" value="username" />
          <add key="LFUser-192.168.1.34-repositoryname" value="password" />
          
      * Finally, optionally, if you would like to have a fallback to try if a connection is made
        from a repository that has not been explicitly configured (or if many of your repositories reuse the same authentication),
        you can specify a default account to try if an account has not been configured for the current repository:
          <add key="LFUser" value="username" />
          <add key="LFPassword" value="password" />

 

Thanks

0 0

Answer

SELECTED ANSWER
replied on August 16, 2016

Hi, Ian,

 

If you want the web service to use a Windows account, you will need to change the Application Pool Identity of the web service:

  1. Open up IIS Manager on the web service machine
  2. In the Connections tab on the left, select the Application Pools node
  3. Select LfSIGNiXAppPool 
  4. Open the Advanced Settings
  5. Under the Process Model section, change the value of Identity to the windows credentials you wish to use
  6. The web service's App Pool will now run using this account
  7. And so the web service will grab these credentials when accessing your laserfiche repository

 

Be sure that the windows account has the necessary Laserfiche repository rights (listed in the documentation) and is a part of the Signix admin group.

 

If you would like to use Laserfiche User credentials, any of the three options you mentioned can work, but I noticed that you did not include the first option that we included in the config (Shown below)

 

* If your repositories across all your servers in your environment are named distinctly (this will be true in most cases),

        you can specify the user/password to use for each repository with just the repository name, like this:

          <add key="LFUser-repository1" value="username" />

          <add key="LFPassword-repository1" value="password" />

          <add key="LFUser-repository2" value="username" />

          <add key="LFPassword-repository2" value="password" />

          etc.

 

So let's say that we have the following credentials:

Username: Alex

Password: LASERFICHEROX

Repository name: MySignixRepository

 

You would add the following lines in the config for the first option:

<add key="LFUser-MySignixRepository" value="Alex" />

<add key="LFPassword-MySignixRepository" value="LASERFICHEROX" />

 

The three other options that you listed would follow the same format, but they just have some extra syntax to handle some side-cases.

For example, if your LFS machine's IP address was 192.168.1.33, you could use:

<add key="LFUser-192.168.1.33-MySignixRepository" value="Alex" />

<add key="LFPassword-192.168.1.33-MySignixRepository" value="LASERFICHEROX" />

 

Don't forget, if you do not want to store your password in clear text in the config, we provided an Encryption tool to encrypt the value of the password. (default location is at C:\Program Files (x86)\Laserfiche\SIGNiX Integration\bin\EncryptionUtility.exe of the web service machine).

 

Hope this helps!

 

-Alex

1 0

Replies

replied on August 17, 2016

Thanks, Alex, this information was exactly what I needed from the windows service change to the syntax of the web.config. 

 

I have gone with the windows authentication and it works. Just need to licence the server now 

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

Sign in to reply to this post.