Installation Requirements (make sure customers know what they're getting into before the install)
AuthAnvil for Office 365 requires an existing validated domain name. This means it needs to have the DNS records configured for O365 ahead of time. If you have already done this, or are using this Office 365 domain already, don't worry about that step.
In order to protect Office 365 we will be federating your domain. This means that all users logging into Office 365 under that domain (i.e. email@example.com) will need to use their AuthAnvil SoftToken to gain access to the web resources. If you are using this in production, I would like to discuss the details of deployment before our session. Your users will need to be prepared for the transition to AuthAnvil 2FA so that they do not lose access once we switch the domain over.
POC Installation requirements
There are a couple of steps to complete before we begin the installation. I have attached the System Requirements guide to prepare the target web server. These prerequisites will need to be in place before we start our session to configure the products.
Our team will also need to set up an account for you in our Customer Portal. This will allow us to activate the software, tying it to a valid account. It will also be where we download the tokens for the Proof of Concept, so you are able to properly authenticate with AuthAnvil resources.
When we configure protection for Office 365, authentication will be directed to AuthAnvil. To properly handle this authentication, IIS will need to have a proper third-party SSL certificate configured on the AuthAnvil site allowing a secure, external connection to the web server.
Keep in mind that, since AuthAnvil will be handling all authentication, users will need to have two-factor authentication set up before they can log in. For this reason we recommend a Proof of Concept be done on a secondary or "test" domain in Office 365, rather than a primary production domain. We do not want any unnecessary interruption from testing the configuration. Please let me know if this a possibility for your environment, or if you would prefer to configure this on a production domain.
I would be glad to discuss these details with your further. As a brief recap, here are the next steps:
- Third party SSL certificate on the AuthAnvil website
- Customer Portal account (created by us)
- System prerequisites (see attached)
- Secondary domain ready (or proper precautions for primary domain)