Walk-through for RSA SecurID Authentication for TMG 2010 Part 1: RSA Authentication Manager 7.1 Server Configuration

 

Disclaimer: Many of the steps outlining the configuration of the RSA Authentication Manager v 7.1 software are not directly supported by Microsoft. They should be used as a guideline to help familiarize and guide you in this configuration. For additional assistance in directly configuring the RSA Authentication Manager Software, please review your RSA SecurID documentation.

• Creating Users and Authentication Agents

• Import Tokens from Seeds files

The seed can be an *.asc or *.xml file and is typically supplied with the token<s>. The seed is the tokens’ factory encoded random key. Each token has a unique key (seed). The seed file is imported into the associated RSA Authentication Manager server.

• Add users and assign a Token to each user

User accounts information is added to the RSA Authentication Manager. New users are created under the ‘Identity’ tab using the RSA Security Console. These accounts can be AD accounts or manually created. Each account created is assigned a Token.

• Synchronize the Token

Each Token has a built-in clock that must be in sync with the RSA Authentication Managers’ clock. If the Tokens’ clock is out of sync, authentication will fail. It is typically a good idea to synchronize the Token after assigning it to a user.

• Create Authentication Agents

Authentication Agents are servers or devices that directly authenticate against the RSA Authentication Manager. In this case, the ‘Authentication Agent’ is the TMG server <s>. You should create a unique ‘Authentication Agent’ for each TMG server in the array.

• Use the resolvable FQDN for the Agent Host

When creating the Agent Host entry, make sure to use the Fully Qualified Domain Name of the ISA server. Also make sure that the RSA Authentication Manager server can correctly resolve this FQDN to the correct internal IP address of the TMG server <s>.

• Select “Standard Agent” as the Agent Type

 

• Create Configuration File (sdconf.rec) and Node Secrets

• Create SDCONF.REC file for each Authentication Agent (each TMG Array Member)

A global SDCONF.REC is generated that contains information for each Authentication Agent. The SDCONF.REC contains RSA Authentication Manager configuration information. This includes ports, processes, etc., essential to the authentication service.

• Copy the SDCONF.REC file from the RSA Authentication Manager to its matching Agent Host computer (i.e. TMG Array Member). Copy to …\system32 and ..\Microsoft TMG Server\sdconfig.

• Create the Node Secrets. The Node Secret is used to authenticate the Authentication Agent machine with the RSA Authentication Manager server. You need to create a separate Node Secret for each Authentication Agent. (Note: There are two separate options available)

1. On the RSA Authentication Manager Server

   • Manually create a node secret for each Authentication Agent. Manually creating a Node Secret on the RSA server creates a file call NODESECRET.REC.

   • Copy each NODESECRET.REC to the matching Authentication Agent machine (i.e. TMG Server) (Note: location you copy to is not important)

   • Copy AGENT_NSLOAD.EXE from the RSA Server to each TMG Array Member (Note: location you copy to is not important)

2. On the TMG Array Members

   • Automatically create Node Secrets using SDTEST.EXE on the TMG Array Members (details to follow)

 

Author

Richard Barker - Sr Security Support Escalation Engineer, Microsoft CSS Forefront Security Edge Team

Comments

• Anonymous
  January 05, 2012
  Can i install RSA Authentication Manager on Hyper-V? Many thanks

• Anonymous
  August 21, 2015
  Yes you can, Maz.