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

Question

Question

What's the "correct" way to create multiple WebLink directories?

asked on September 21, 2018 Show version history

Hello,

I've read several Answers posts and this documentation, but I feel like I'm findng conflicting information about how to properly configure multiple virtual directories in WebLink.

I know that in the current version of IIS you need to create a separate application instead of virtual directory, and I managed to get closer to a working configuration, but I'm still running into problems.

 

Some recent posts from LF suggest pointing both at the same folder path; when I tried this way, the second instance won't load a default page.

 

The documentation on the other hand recommends copying the files to a separate folder; this worked for everything except LFDS authentication.

When I tried enabling LFDS authentication, one of two things happen; 1) The STS page redirects to a "localhost" URL, or 2) It gets stuck in a redirect loop.

 

So, what is the correct/approved way to configure multiple directories when using LFDS authentication in WebLink 10.1?

1 0

Answer

SELECTED ANSWER
replied on September 24, 2018

Hello Jason,

 

Below is how you would configure a LFDS to work with multiple directories in WebLink.

With this type of configuration it is a little more tricky. You will need a separate folder path for your WL directory.

1) Copy the ..\Laserfiche\WebLink\WebLink\Web Files to another location say... C:\Sales_WebLink\

2) Point your new IIS application, say WebLinkSales, to that new directory of C:\Sales_WebLink\ (as an example)

3) Within the C:\Sales_WebLink\ (once again, as an example), look for the web.config directly underneath this folder (where this folder is "Sales_WebLInk").

4) look for <system.identityModel.services> 

you will see 2 lines underneath...

<cookieHandler requireSsl="true" name="LFAuth" path="/weblink" />

 

Change the path to your desired virtual Directory name. So if your application name is "WebLinkSales", you will change the "path" to...

path="WebLinkSales" 

 

Let me know if you run into any other complications. 

Regards,

AChan

 

4 0
replied on September 24, 2018 Show version history

Thanks! That seems to have done the trick!

Some additional steps for anyone looking to do the same thing:

  • When you create your new Application, go into "Default Pages" and add "Welcome.aspx" (or your preferred default) to the top of the list
  • When you register the new page/site, make sure you set the URL based on your new application name

 

Update: I put together a document outlining the new steps and figured I would share it here just in case anyone else needs to do the same thing.

Update: Make sure to check the folder permissions. We had issues saving settings in the designer, and it turned out to be permissions on the new folder.

9 0
replied on September 30, 2019

What permissions did you need to set on the new folder?

0 0
replied on October 1, 2019

Our engineers set up the permissions, but I believe the IIS user for the site would need at least read and write privileges to save setting changes. You could always check the IIS user account's permissions on the main WebLink folder and replicate those.

0 0

Replies

replied on January 14 Show version history

Thank you for the document, Jason. I did run into an issue when trying to use the WebLink Designer to update the Theme. By default, there is not a Custom folder created in the \WebFiles folder so the designer will give you an error message. Copy the Custom folder from your default WebLink site and paste it in. If you don't see one, make a Theme change and save it and it will create one and then you can copy it over after that.

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

Sign in to reply to this post.