Now that Microsoft have released ISA Server 2006, we have more authentication options available to us. This includes the ability to add two-factor authentication solutions to the existing forms based authentication, traditionally used to authentication against Active Directory only. I have a previous post on how to protect Outlook Web Access with RSA SecurID, which discusses using the RSA Web Agent with IIS and RSA SecurID authentication with ISA Server 2004, however both of those options are a little clunky. Now with ISA Server 2006, we have a more elegant solution that allows us to integrate RSA SecurID directly into the forms authentication method. Assuming ISA Server is a domain member, here’s how to do it.
First off, I’ll discuss how SecurID authentication works in ISA Server. Microsoft have licensed the agent software from RSA and offered RSA SecurID authentication since ISA Server 2000 Feature Pack 1. This is built into the product and does not require a separate agent installation. As of ISA Server 2006, the SecurID agent version is 18.104.22.168. You can view the support DLLs in the ISA Server program folder (Program FilesMicrosoft ISA Server, aceclnt.dll, sdmsg.dll and sdui.dll).
To allow the ISA Server to authenticate against the RSA ACE server, an agent host record needs to be created (assuming a Windows box is hosting the ACE server):
- Log onto the RSA ACE server and start the Database Administration tool in Host Mode
- Add a new agent host and use ‘Net OS Agent’ as the agent type
- Enable the tick-box labelled ‘Open to All Locally Known Users’ if you want all users to be able to authenticate
- Click OK to save the changes and copy SDCONF.REC (located in
C:\Windows\SYSTEM32) to ISA Server.
Configuring SecurID support in ISA Server as a simple process:
- Copy SDCONF.REC to
C:\Windows\SYSTEM32.The ISA Server help file says to put this file into the ISA Server program folder, but this worked fine for me in the SYSTEM32 folder.
- Ensure that the local account NETWORK SERVICE has Full Control to the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\SDTI. This is so that ISA Server can write the secret to the registry.
- You may also need to add the PrimaryInterfaceIP string value to the registry under
HKEY_LOCAL_MACHINE\SOFTWARES\DTI\ACECLIENTdepending on your ISA Server configuration. The value must match that set in the agent host record.
You can test RSA SecurID authentication with the RSA Test Authentication utility available from the Microsoft web site. Download this utility and copy the extracted utility to the ISA Server program folder and execute from there (if you don’t you will receive an error).
Now that the SecurID authentication requirements have been configured you can create a web publishing rule to enable access to Outlook Web Access. This is a simple wizard driven interface (use the Exchange Web Client Access Publish Rule wizard) and is discussed in detail in ISAServer.org so I won’t go into detail here.
Once the rule and a corresponding web listener has been created, you will need to edit the properties of the web listener:
- Choose the Authentication tab and ensure that ‘HTML Form Authentication’ is selected as the authentication method
- Enable the tick-box labelled ‘Collect additional delegation credentials in the form’
- Then select the radio button labelled ‘RSA SecurID’
- Click OK and apply your configuration changes.
Now you should have three fields listed on the Outlook Web Access authentication page: username, token code and password. ISA Server also provides for a scenario where the RSA username and the Windows username are different, adding a forth field for a Windows username.
This is an excellent method of taking authentication that one step further to ensure only trusted users have access to your corporate resources. The same authentication options offered in ISA Server also allow for other two-factor authentication solutions via RADIUS OTP (One Time Password). With this option you could authenticate against Secure Computing’s SafeWord PremierAccess or Verisign’s Unified Authentication to provide two-factor authentication.
One thing to note about enabling RSA authentication on your OWA rule, if you also use this rule for ActiveSync, this will break ActiveSync. I have not looked into this further, but I would recommend creating a separate rule for ActiveSync using a second certificate.