Configuring a redundant AuthAnvil server

To setup a redundant AuthAnvil Server we will need at least three separate servers. 

  1. Dedicated server for the SQL Database.
  2. Web server 1. Example domain
  3. Web server 2. Example domain

Web Server 1 & 2 will need to be configured with the system requirements including a unique third party trusted SSL certificate.



Server 1

This web server is built using the latest installers for 2FA/SSO/PWS.

Note: At the time of this article these are the latest versions.
Two-Factor Auth v5.5
Single Sign On v4.5
Password Server v2.7

Once Server 1 is configured we create a CLu file


Server 2

We copy the .CLU file from Server 1 to Server 2 and use the latest installers for Two-Factor Auth & Password Server. During the install there will an option to install to an existing cluster. Using this install option Server 2 is configured automatically to work with the same Database as Server 1.


You will now have two unique SAS URL's that will look something like this. &

You can configure a Windows Credential Provider or RADIUS server with these two unique URL's to automatically fail-over.


High availability

To take this one step further you may also want to configure a Network Load Balancer (NLB) with a unique SSL certificate.

For example
Server 1:
Server 2:

This would allow you to navigate to your SSO portal as and have it fail-over automatically between Server 1 & Server 2.





If you have any questions or need some help, we would be happy to assist. Open a case at or send an email to

Have more questions?

Contact us

Was this article helpful?
0 out of 0 found this helpful

Provide feedback for the Documentation team!

Browse this section