MFA Guides

Environment Setup and Timestamps

When setting up environments with multiple servers, such as the use case of configuring RapidIdentity MFA Server to work with a DMZ, it is important that all servers in the environment use the same timestamps and timezone settings.

For help in configuring the time settings, see Windows Time Service Tools and Settings.

The purpose of this guide is to facilitate RapidIdentity MFA installation and setup.

RapidIdentity MFA is a collective name to describe two core technologies: RapidIdentity Server and RapidIdentity Client, the latter of which can be a Windows Client or Mac Client. RapidIdentity Server is the server component to the MFA components. RapidIdentity Windows Client and RapidIdentity Mac Client are fat clients providing the MFA functionalities.

This guide provides a complete, technical description of the basic installation process starting with core infrastructure (e.g. Microsoft Active Directory) and ending with configuring RapidIdentity MFA.

The installation procedures include six focus areas.

  1. System requirements

  2. Installing core infrastructure

  3. Core infrastructure post-installation procedures

  4. Installing RapidIdentity Server

  5. Configuring RapidIdentity Server

  6. Installing and configuring client-side infrastructure

When the installation process is complete, RapidIdentity MFA enables administrators to perform actions in a browser-based application on Microsoft IIS and uses Microsoft SQL Server or SQL Server Express as a repository.

This solution enables both administrators and users to administer and access credential-based information from browser-based portals.

RapidIdentity MFA  significantly reduces the complexity of credential management and provides enhanced usability.

RapidIdentity Server is installed on Microsoft Internet Information Services (IIS). Consequently, IIS must be available at all times. In production environments, Identity Automation recommends considering High Availability (HA) and failover for the IIS server. Securing Microsoft IIS is recommended although its procedure is beyond the scope of this guide.

RapidIdentity Client uses local cache for offline login, however, it must have successfully performed one synchronization event with the RapidIdentity Server running on IIS.

RapidIdentity MFA is essential for credential issuance and credential lifecycle management events. Administrators gain access in order to change management and basic administration.

To help streamline installation and provide meaningful context, this guide is tailored specifically for RapidIdentity Server’s use with smart cards, contactless cards, and knowledge-based authentication.