Please review the following information to see if you meet minimum system requirements to use the AuthAnvil Password Server. The AuthAnvil Password Server supports the following operating systems:
Supported Operating Systems
- Windows Server 2008 x64 (SP2)
- Windows Server 2008 R2
- Small Business Server 2008 (SP2)
- Small Business Server 2011
- Windows Server 2012
- Windows Server 2012 R2
- Windows Server 2012 Essentials
- Microsoft Internet Explorer 10 or later
- Microsoft Installer Services (MSI) 3.0
- Web Server (IIS) with the ASP.NET role enabled
- (Server 2012) Windows Identity Foundation 3.5 must be installed as a server Feature
- (Server 2012) HTTP Activation server Feature under .NET Framework 4.5 Features -> WCF Services
Prerequisites Installed by the Installer
- Microsoft .NET Framework v4.5.2
- Microsoft SQL Server Native Client
- Microsoft SQL Server System CLR Types
- Microsoft SQL Server Management Objects
- Microsoft SQL Server Express 2014 configured to use mixed mode authentication (if requested by the user)
- The server must have a working internet connection in order to download AuthAnvil Password Server components and prerequisites.
- Installation requires that the user installing must have administrative privileges on the domain (or local machine if not domain joined).
- The user installing's Windows Account must have administrative permissions for the SQL server.
- If you are installing AuthAnvil on a separate server from the SQL server, impersonation is supported on either domain joined servers or servers that are members of the same workgroup.
- The AuthAnvil Password Server is officially supported on servers and workstations where the base OS was installed in English (CA/US/UK/AU). Scorpion Software cannot make guarantees to successful operation on other international languages that have not officially been tested.
- We strongly recommend that the web site that AuthAnvil is deployed to has an SSL certificate installed. HTTP connections to the web interface are recommended for testing purposes only. However, the server must allow HTTP connections, as communications between the web interface and the back-end web service are securely handled over HTTP with message-level encryption, which cannot communicate over an SSL channel.