1. Product Documentation
This document is an installation guide for the OpenOTP Authentication Provider for AD FS 3.0 / 4.0. Hence, the installation or configuration of WebADM, including token registration is not covered in this guide. For installation and usage guides to WebADM refer to the RCDevs WebADM Installation Guide and the RCDevs WebADM Administrator Guide available through the RCDevs’ online documentation library.
2. Product Overview
The OpenOTP Authentication Provider for AD FS is a component that integrates the RCDevs OpenOTP one-time password authentication into an Active Directory Federation Services server, adding OpenOTP authentication as a possible MFA option in the AD FS Management tool. RCDevs OpenOTP Authentication Server is a WebApp that is tightly coupled to the RCDevs WebADM application server. The Authentication Provider enables you to use all types of authentication tokens and authentication standards supported by the OpenOTP authentication module. That includes OATH/HOTP, OATH/TOTP, OATH/OCRA, Mobile-OTP, YubiKey, SMSOTP, MailOTP. Software tokens are provided by various publishers and for a variety of platforms including Android and iOS.
3. System Requirements
The OpenOTP Authentication Provider has to be installed on the Windows servers with an AD FS role. Your environment should fulfill the following requirements:
- Windows 2008 or later.
- Network access.
- An instance of WebADM and OpenOTP running in your network.
- Permanent connection to OpenOTP server’s network API.
- DNS suffix set to match your AD domain.
4. Preliminary Information
Administrative/elevated permissions are necessary on any server to correctly set up and/or change the OpenOTP Authentication Provider’s configuration. To correctly setup the provider, please gather the following information. You will need to enter during the installation process:
- The URI(s)s of the OpenOTP web-service(s) (mandatory).
- These URIs are mandatory, due to the client needs to know where the OpenOTP SOAP network API can be reached. They are entered as a comma-separated list. At least one URI is necessary.
- Your local domain (optional). Needed to force a domain, which is not set as default on the OpenOTP side.
- A custom login text or tile caption (optional). A text that is displayed on the AD FS login pane.
- A client ID (optional). An ID to identify this part of your infrastructure to OpenOTP, allowing to modulate OpenOTP’s behavior with client policies.
- A certificate authority (CA) file (optional).
- A certificate file and the certificate password (optional).
- A custom settings string (optional).
- SOAP timeout delay (optional).
OpenOTP plugin for ADFS works for ADFS 3.0 & 4.0 (earlier than Windows server 2008) If you have an older version, you have to update your ADFS infrastructure.
5. Installation and Configuration
In this post, we will assume an existing ADFS infrastructure installed and available. This post will not cover how to setup ADFS. Please refer to the Microsoft documentation and/or the TechNet blog for details about how to install and configure ADFS Microsoft | TechNet. For this recipe, you will need to have WebADM/OpenOTP installed and configured. Please, refer to WebADM Installation Guide and WebADM Manual to do it.
Before running the MSI file, please stop your ADFS services.
The OpenOTP plugin for ADFS must be installed on every ADFS server. Please download the plugin from the RCDevs Website.
Extract files from the archive on your ADFS server(s) and run the MSI file and click on
MSI file should be run with domain admin rights. To be sure that you have the good permissions, you can execute the MSI file through powershell in “Run As Administrator” mode.
Accept End-User license Agreement and click on
Next. On the next page, choose your default folder location and click on
On this page, you have to configure the OpenOTP SOAP URL(s). Your WebADM SOAP endpoint should be:
https://your-web-adm-ip-address-or-dns-name:8443/openotp/. You can also configure a message for the end-user login page. Click on
On the next page, every configuration are optional. If you’d like to use a client certificate for enhanced security, please use this next screen to provide the detail.
Clicking on the question marks (?) will provide additional help during the installation procedure.
On the next page, you can configure a custom message when users need assistance. For example :
Next page allows you to configure failover with OpenOTP, SOAP request timeout and UPN Mode.
Keep the default configuration if you are not sure of what you need. Click on
Here you may set up a custom settings string for your WebADM and OpenOTP configuration. Furthermore, you may change the default SOAP service timeout.
If two server URLs are defined in server URL, you can optionally configure a request routing policy (i.e. the server selection policy).
There are three policies available:
Ordered: The first server is always preferred. When it does not respond, the second server is used.
Balanced: The server is chosen randomly for each request. When it does not respond, the other is used.
Consistent: The server selection depends on the user ID. A request for one specific user is also always routed to the same server. If it does not respond, the other server is used.
Next when you are done.
On the next screen, you have to register the OpenOTP service in your ADFS instance. The registration should be done only once per ADFS instance. Click on
Yes if it’s the first time you install OpenOTP ADFS plugin. For the others, ADFS servers in the same instance, click on
No. ADFS services should be running during the registration.
Installation is complete. Click on
Don’t forgot to restart ADFS services when your installation is done.
Repeat this procedure on every ADFS servers!
6. ADFS Configuration for Multi-Factor Authentication
In this documentation, we enable OpenOTP Multi-Factor authentication on the default ADFS login page. This page is disabled by default. Have a look to Technet Microsoft to enable the ADFS login page.
6.1 Configuration for ADFS 3.0
Now, we will configure the ADFS server(s) to have multi-factor authentication. For this, go on Windows Server Manager, click on Tools and ADFS Management.
On the ADFS Management page, right click on Authentication Policies and click on Edit Global Multi-factor Authentication…
On the next page, you will find a new option available in the additional authentication methods named “RCDevs OpenOTP Authentication Provider”. Check the box of this option and click on
Your ADFS server is now configured with OpenOTP. You can go on your ADFS login page :
Sign in button, enter your credentials and click on
On the next page, an OTP will be asked.
Here, AD FS was configured so that OpenOTP is the only option for a secondary factor, and OpenOTP is configured to require an OTP sent by mail to the user only. Enter your secondary factor to complete the test.
OpenOTP User Activation
Your account should be activated for OpenOTP. Look the following ‘How To’ to activate an account : OpenOTP User Activation. A Token has to be enrolled on the user account before testing OTP authentication.
6.2 Configuration for ADFS 4.0
Now, we will configure ADFS server(s) to have multi-factor authentication. For this, go on Windows Server Manager, click on Tools and ADFS Management.
On the ADFS Management page, under
Service right click on
Authentication Methods and click on
Edit Multi-factor Authentication Methods.
On the next page, you will find a new option available in the additional authentication methods named
RCDevs OpenOTP Authentication Provider. Check the box of this option and click on OK.
Multi-factor policies at the ADFS level will now contact RCDevs plugin for MFA authentication.
We will now create a Multi-Factor policy called
OpenOTP. Right click on Access Control Policies under the ADFS management console and then click
Add Access Control Policy.
Name your Access Control Policy, on my side
OpenOTP and click on
Add button to configure the policy. On my side, I will allow every user and require a multi-factor authentication.
This part is done, you can click on
We will now configure a relying party trusts on the ADFS to apply our policy to the default ADFS login page (https://ADFS_INSTANCE_NAME/adfs/ls/idpinitiatedsignon)
Right click on
Relying Party Trusts and click on
Add Relying Party Trusts.
You are now in
Relying Party Trusts Wizard.
On the first page, select the option
Claims aware and then click
On the next screen, you have to select the data source. Choose the 3rd option to configure the data source manually and click
On the next screen, name your Relying Party and click on
The next configuration page is optional. If required configure it and click on
On the next page, select
Enable support for the SAML 2.0 WebSSO protocol and configure your URL according to your ADFS server and click on
On the next screen, you have to configure your Identifier. Configure your Identifier, click
On the next configuration page, you have to choose an access control policy. I have previously created a policy called
OpenOTP so I choose this one :
The configuration of the Relying Party Trust is now finished. Click on
Multi-Factor Authentication is now configured for the default ADFS login page.
We will now perform an authentication.
Click on Login and the next page will prompt you the following :
Click on Continue button and the next page will ask you to enter your OTP :
Provide your OTP and you are logged on.
7. Uninstalling the OpenOTP Authentication Provider
If you ever decide to uninstall the provider, simply re-run the installer and choose “Remove”.
To pinpoint a problem in your AD FS/OpenOTP setup, you can start with the Windows Event
Viewer: “Applications and Services Logs”, then “AD FS”, then the “Admin” log.
Also look at
/opt/webadm/logs/webadm.log, or the equivalent in the WebADM interface (under the “Database” section).
9. Video Demonstration
Play Video on Youtube