Mi-Token Reporting provides valuable insight into your 2-factor authentication environment, with detailed reports on authentication activity, user behavior, and system health. Here are the key steps to install Mi-Token Reporting:
- Prerequisites Ensure your server meets the prerequisites, including a supported version of SQL Server (2005, 2008, 2012, or 2014), IIS web server role, and .NET Framework 4.0+. The server should have connectivity to the Mi-Token authentication server(s).
- Run the Installer Log in with an account that has local administrator and SQL Server admin privileges. Run the Mi-Token Reporting installer executable. If SQL Server is on a different machine, ensure the firewall allows access on the configured port (default 1433).
- Set Up Permissions The installer will attempt to automatically grant the required permissions to the service account. If this fails, refer to the documentation for the manual steps to assign the appropriate SQL Server and file system permissions.
- Configure ODBC Connection Launch the Mi-Token Reporting configuration tool. Click "Create Data Source" to set up the ODBC database connection. Specify the SQL Server instance name, database name (default is Mi-Token), and authentication mode (Windows or SQL auth).
- Register Mi-Token Servers In the Reporting setup tool, go to the RADIUS Servers tab and click "Add" to register each of your Mi-Token authentication servers. If the Reporting database is on a separate machine from a Mi-Token server, you will need to manually configure event log permissions on that server using the provided PowerShell commands.
- Install Event Collector From the Event Collector tab, click "Install" to install the Mi-Token Event Collector Windows service. This service collects authentication events from your Mi-Token servers and stores them in the SQL database.
- Install Reporting Website From the Reporting Website tab, click "Install". Select the website and virtual directory to install the reporting application under (default is Default Web Site/mitoken-reports). The installer will create a self-signed SSL certificate for HTTPs access.
- Configure Email Alerts (Optional) To configure the Reporting system to send email alerts, edit the ReportingAlert.exe.config file to set the SMTP server details and alert frequency.
- Verify and Use Open a browser and go to the Reporting website URL (e.g. https://server/mitoken-reports). Log in and verify that authentication data is being collected and displayed. You can now use the Reporting interface to view data and generate reports.
With those steps, your Mi-Token Reporting system should be up and running, giving you valuable visibility into your 2FA environment. The initial setup may take some time, but the insight gained is well worth it. Refer to the documentation for additional details on configuring and using Mi-Token Reporting.