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

Question

Question

Setup Laserfiche application(s) on separate IIS websites

asked on January 13

I have one IIS installation supporting multiple Laserfiche applications (note: LFAPI, Webclient, Forms). I can't use virtual directories because I want to use different bindings. Is there documentation or can it be provided detailing setting up a Laserfiche application as a separate website? My ultimate goal is to have one of the applications available externally and others internal only.

0 0

Replies

replied on January 13

What you're attempting, could probably be easier accomplished with a separate server VM.

0 0
replied on January 13

I strenuously recommend this approach. It's also cleaner for security purposes.

The only Laserfiche web application that supports any sort of "multi-instance on server" deployment is WebLink with virtual directories. 

Do not attempt with any other Laserfiche web app. Not supported.

1 0
replied on January 13

Follow-up in case the scenario is something like "I want Forms to be external and Repository Web client to be internal" rather than "I want multiple instances of $app".

Still don't do that. Use a separate VM for separation of security concerns.

Alternatively, use a layer 7 http reverse proxy/load balancer that supports path-based routing to provide the external endpoint, and add routing rules that only allow access to a specific app like so (pseudo-code):

# Routing rules processed in sequential order until match found

# block /FormsConfig access - must be first to take priority over /Forms* rule
1. if (host = external.example.com & path = /FormsConfig*) {return 404} 

# allow /Forms traffic
2. if (host = external.example.com & path = /Forms*) {route to $webServerBackend} 

# allow login page access if necessary
3.  if (host = external.example.com & path = /LFDSSTS/*) {route to $webServerBackend} 

# default/fallback rule
4. else {return 404}

-Sam

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

Sign in to reply to this post.