Both Windows & Form Authentication Options
sjohnson
Member IT Monkey ✭
Is it possible to have both Windows & Form Authentication options?
Option 1: Install the portal 2x on the same server, different IIS site
Option 2: Install the portal on 2 different servers, one Windows Authentication other Forms authentication
What I'm trying to accomplish is for internal users they get the Windows Authentication site for external users they get the form authentication site.
I know how to do the routing part, just need to know what is the best option installing.
Also would I only run Cache Builder on 1 server if I went with option 2?
Option 1: Install the portal 2x on the same server, different IIS site
Option 2: Install the portal on 2 different servers, one Windows Authentication other Forms authentication
What I'm trying to accomplish is for internal users they get the Windows Authentication site for external users they get the form authentication site.
I know how to do the routing part, just need to know what is the best option installing.
Also would I only run Cache Builder on 1 server if I went with option 2?
0
Best Answer
-
Adam_Dzyacky
Product Owner Contributor Monkey ✭✭✭✭✭
I actually raised this identical discussion awhile ago myself (https://community.cireson.com/discussion/485/portal-internal-or-external#latest).
In general, there should be nothing stopping you from from installing the site twice on the same IIS host and routing it differently. With respect to cachebuilder, you can't run multiple instances as it doesn't understand how to do that level of micro-management - so this is to say that yes, option 1 is only going to require a single running instance of the cachebuilder.
Back in the "Travis Days" of Cireson, I know he suggested deploying it on multiple servers but obviously only running it once. This was suggested so that in a failover scenario the service existed to be started.5
Answers
In general, there should be nothing stopping you from from installing the site twice on the same IIS host and routing it differently. With respect to cachebuilder, you can't run multiple instances as it doesn't understand how to do that level of micro-management - so this is to say that yes, option 1 is only going to require a single running instance of the cachebuilder.
Back in the "Travis Days" of Cireson, I know he suggested deploying it on multiple servers but obviously only running it once. This was suggested so that in a failover scenario the service existed to be started.