Windows Logon
With the Akamai Windows Logon plugin, you can add Akamai MFA as the secondary authentication step to protect all Windows logins including the Remote Desktop Services (RDS). As a result, when signing in to their Windows devices, users have to first authenticate with their Windows credentials. Next, Akamai MFA challenges users with the secondary authentication request using the factor they enabled on their enrolled mobile device.
See this diagram that presents a conceptual model of the authentication process. For clarity reasons, some traffic flows are not covered.
-
The user establishes an RDP connection to the Windows server with remote desktop services enabled (further referred to as Windows server).
-
The Windows server prompts the user to log in using their credentials.
-
Active Directory confirms that the primary authentication was successful.
-
Upon successful authentication, the Windows server, using the Akamai plugin, establishes a connection over TCP port 443 and redirects the user to Akamai MFA.
-
Akamai MFA challenges the user with secondary authentication.
-
The user confirms their identity using the selected secondary authentication method.
-
Akamai MFA redirects the user to the Windows server.
-
The Windows server allows the user to proceed to the protected application.
Before you begin
-
This integration communicates with the Akamai MFA service on TCP port 443. Your firewall must allow outbound connections from your environment to the Akamai MFA host.
If your environment has a firewall that restricts outbound connections, Akamai provides a dedicated hostname (static.mfa.akamai.com) with a permanent list of static IPs. To ensure stable and reliable connectivity, add these IP addresses to your allowlist:- IPv4 addresses for
static.mfa.akamai.com:
23.11.42.61 23.11.43.61 23.11.38.62 23.11.39.62 23.11.40.61 23.11.41.61 23.11.32.63 23.11.33.63 23.11.36.61 23.11.37.61 23.11.34.62 23.11.35.62- IPv6 addresses for
static.mfa.akamai.com:
2600:14e1:28:26::/64 2600:14e1:2c:26::/64 2600:14e1:18:27::/64 2600:14e1:1c:27::/64 2600:14e1:20:26::/64 2600:14e1:24:26::/64 2600:14e1:0:26::/64 2600:14e1:4:26::/64 2600:14e1:10:26::/64 2600:14e1:14:26::/64 2600:14e1:8:26::/64 2600:14e1:c:26::/64
- IPv4 addresses for
Your <API Host> is available in the Akamai MFA Integrations configuration page.
-
To enable this integration for users, ensure that they have either local or domain user accounts. The users' Windows login names have to match their Akamai MFA user names. Also, make sure that the users are enrolled in Akamai MFA and their registered mobile devices have been activated.
-
Prior to the installation of the plugin, ensure that your server is correctly synchronized with an internet time source. Otherwise, you may be presented with a time-based error when attempting to use Akamai MFA.
System requirements
The Windows Logon plugin supports the following client and server operating systems on both x64 and ARM64 architectures:
Clients
- Windows 10, version 1803 or later
- Windows 11
Servers
- Windows Server 2016
- Windows Server 2019
- Windows Server 2022
- Windows Server 2025
Make sure you've installed the latest Microsoft updates before installing the plugin.
Add Windows Logon integration
Follow this procedure to generate the integration credentials that are required for the Akamai MFA Windows Logon plugin. These credentials enable communication between Akamai MFA and the Windows server.
-
In the Enterprise Center navigation menu, select Multi-factor Authentication > Integrations.
-
Click Add integration (+).
-
In Integration Type, select Windows Logon.
-
In Name, enter a unique name for your Windows Logon integration.
-
Click Save and Deploy.
You’ve just generated your API Host, Integration ID, and Signing Key. You provide these credentials when you install the Windows Logon plugin.
This data is available for you on the integration page. You can copy these credentials at any time.
Your Signing Key should be kept completely secret like any other password or secret key credential.
Install the Akamai MFA Windows Logon plugin
Follow these steps to install the Windows Logon plugin for Akamai MFA using the installation wizard.
Before you begin
The installer requires .NET Framework 4.7.2 or later, which is preinstalled on Windows 10 version 1803, Windows 11, Windows Server 2019, and later. Windows Server 2016 requires a one-time .NET Framework 4.7.2+ installation before running the installer.
How to
-
Download the universal
AkamaiMfaCredentialProviderLatest.exeinstallation package. The installer supports x64 or ARM64 and also includes the .NET 10 Desktop Runtime. -
Navigate to your downloads folder and open the
AkamaiMfaCredentialProviderLatest.exeinstaller package. The .NET 10 Desktop Runtime is installed if it is not already available on the system. -
In the installer welcome dialog, click Next.
-
Review and accept the End-User License Agreement, and then click Next.
-
In the installer configuration dialog, enter the API Host that you generated. You can copy this information from the Akamai MFA integration page.
-
(Optional) Select Disable certificate revocation list (CRL) check to turn off the certificate revocation check. Leave this option cleared unless your network blocks the plugin from checking certificate revocation. For more information, see Certificate revocation checking.
-
(Optional) Select Configure a manual proxy for Akamai MFA traffic to use an outbound proxy for Akamai MFA traffic. Specify your Proxy Host and Proxy Port, and then click Next.
-
Enter the Integration ID and Signing Key that you generated. You can copy these credentials from the Akamai MFA integration page. Click Next.
-
Select which login attempts you want to protect by adding Akamai MFA as the secondary authentication step:
- Select Remote Logon Only if you want to add Akamai MFA only to remote sessions.
- Select Remote and Console Logon if you want to add Akamai MFA to both local and RDP Windows logins.
-
(Optional) Select Apply policy to RDP client IP address instead of host IP address to evaluate the originating RDP client's IP address against your policy. Use this option only when the RDP client is a trusted source such as an RD Gateway server on a private network.
-
Click Install to start the installation.
-
Wait for the installation process to complete and click Finish.
The Windows Logon plugin for Akamai MFA is installed. Now, you can test your configuration.
Silent install
Follow these steps to silently install the Windows Logon plugin for Akamai MFA using the command line.
Before you begin
The installer requires .NET Framework 4.7.2 or later, which is preinstalled on Windows 10 version 1803, Windows 11, Windows Server 2019, and later. Windows Server 2016 requires a one-time .NET Framework 4.7.2+ installation before running the installer.
How to
- Download the
AkamaiMfaCredentialProviderLatest.exeinstallation package. - Open the command line (
cmd). - Navigate to your downloads folder, for example
cd C:\Users\Username\Downloads. - Prepare your integration credentials and proxy settings. The installer accepts the following parameters:
| Parameter | Meaning |
|---|---|
APIHOST=<host> | Required. Specifies the API Host. You can find this information in Enterprise Center by navigating to the RDP integration page. |
DISABLECRL=<1 or 0> | Optional. Specifies whether to turn off the certificate revocation check. The check is enabled by default. See Certificate revocation checking. Values:
|
MANUALPROXYENABLED=<1 or 0> | Optional. Specifies whether to use an outbound proxy for Akamai MFA traffic. Proxy is disabled by default. Values:
|
PROXYHOST=<manual_proxy_host> | Optional. With manual proxy enabled, specifies your proxy host. |
PROXYPORT=<manual_proxy_port> | Optional. With manual proxy enabled, specifies your proxy port. |
APPID=<integration_id> | Required. Specifies the Integration ID. You can find this information in Enterprise Center by navigating to the RDP integration page. |
SIGNINGKEY=<signing_key> | Required. Specifies the Signing Key. You can find this information in Enterprise Center by navigating to the RDP integration page. |
REMOTEONLY=<1 or 0> | Required. Specifies if local logins are allowed. Defaults to 1.Values:
|
EVALUATEREMOTEIP=<1 or 0> | Optional. Evaluates your policy against the originating RDP client's IP address instead of the host's IP address. Use this option only when the RDP client is a trusted source such as an RD Gateway server on a private network. Disabled by default. Values:
|
In addition to the configuration parameters above, the installer accepts the following command-line switches:
| Switch | Meaning |
|---|---|
/quiet | Runs the installer with no UI and no prompts. |
/uninstall | Uninstalls the plugin instead of installing it. |
- Launch the installer from an elevated command prompt. For example, you may enter the following command to silently install the plugin and set it to use a proxy server:
AkamaiMfaCredentialProviderLatest.exe /quiet APIHOST=mfa.akamai.com APPID=app_1234 SIGNINGKEY=abcd REMOTEONLY=1 MANUALPROXYENABLED=1 PROXYHOST=198.51.100.0 PROXYPORT=8080- The installation process runs silently. The bundled .NET 10 Desktop Runtime is installed if it is not already present. The architecture-specific plugin that matches the host (x64 or ARM64) is also installed. When the installation process is complete, you can test your configuration.
Certificate revocation checking
Starting with version 4.1.2.0, the Windows Logon plugin checks whether the Akamai MFA server certificate has been revoked before it connects. This check is only performed when the revocation server can be reached. The plugin only rejects certificates that are confirmed as revoked.
You don't need to change your firewall for this check. If your network blocks or delays revocation checks, you can turn off the check by selecting Disable certificate revocation list (CRL) check in the installer or by specifying DISABLECRL=1 in a silent install.
Update your Windows Logon plugin
You can get the latest version of the Windows Logon plugin at AkamaiMfaCredentialProviderLatest.exe. See the release notes for information about other available updates.
If you are running a version earlier than 3.5.9.0, update to the latest version. Newer releases contain important security enhancements.
To update the Windows Logon plugin:
Install the latest version of the plugin using the same Integration ID and Signing Key that you generated when creating the RDP integration in Akamai Enterprise Center.
Test your setup
Before you begin
Enroll your mobile device in Akamai MFA to learn more.
In this step, you will log in to a Windows device to check if the configuration works correctly.
Testing your setup allows you to experience the authentication process.
How to
-
Log in to Windows using your Windows username and password.
-
You're redirected to the Akamai MFA authentication dialog, where you can select the preferred secondary factor.
-
The authentication request is sent to your enrolled mobile device. Click Allow to confirm your identity.
-
Once you successfully confirm your identity, you're logged in to your Windows device.
Offline login
You need to set up your offline authentication policy in Enterprise Center before you can enable this feature.
With offline login, users can complete multi-factor authentication and log in to their Windows device even when it has no internet connection. Each user sets up offline login once while online by scanning a QR code with Akamai MFA or another authenticator app. When the Windows device is offline, the user enters a one-time passcode from that app instead of authenticating with Akamai MFA online.
Enable offline login
Follow these steps to enable offline login on your Windows device.
How to
-
On your Windows login screen, enter your credentials and press Enter.
-
On the authentication dialog, select Enable offline login. When selected, an informational banner displays: Offline login activation will begin after authentication.
-
Select a device and complete authentication. The Offline Login Activation dialog now shows a QR code.
-
Scan the QR code with Akamai MFA or another authenticator app.
-
After scanning the QR code, your authenticator app displays a one-time passcode. Enter that passcode into the 6-digit code input field on your Windows device.
-
Click Activate Offline Login. You are logged in to your Windows session. Next time you log in, you will be able to authenticate offline.
Until you enable offline login, the Activate Offline Login dialog may also appear after you authenticate. Click Activate Now and continue from step 4. If you click Remind me Later or Don't Show Again, you can still enable offline login at any time with the steps above.
Disable offline login
Follow these steps to disable offline login on your Windows device.
How to
-
On your Windows login screen, enter your credentials and press Enter.
-
On the authentication dialog, select Disable offline login. When selected, a warning banner displays: Your existing offline login authenticator will be removed after authentication.
-
Select a device and complete authentication. Your offline authenticator is removed and you are logged in to your Windows session.
To enable offline login again, follow the steps in Enable offline login.
Authenticate with offline login
Follow these steps to log in to your Windows device when you are offline.
How to
- On your Windows login screen, enter your credentials and press Enter. If your Windows device has no internet connection, the Offline Login dialog opens.
- Open your authenticator app to get a one-time passcode.
- In the Offline Login dialog, enter the passcode.
- Click Login. You are logged in to your Windows session.
Offline codes are accepted within the standard RFC 6238 verification window, so a small time difference between your Windows device and your authenticator app doesn't cause a failure.
After you reach the Max logins or Max days offline limit in your offline authentication policy, you may be prompted to authenticate online.
View plugin logs
Starting with version 4.1.2.0, the Windows Logon plugin writes logs to these locations:
- Event Viewer. Warnings and errors appear under Applications and Services Logs > Akamai MFA.
- Session log files. Detailed logs are written to
%SystemDrive%\Windows\Logs\AkamaiMfaCredentialProvider\. Each file is namedcredential-provider_<timestamp>_<process-id>.log. Log files are deleted after 30 days.
Personal data such as phone numbers, email addresses, and IP addresses is masked in the logs. The device list on the authentication dialog also shows masked phone numbers and email addresses.
Updated 12 days ago
