Home > Active Directory, RSA > How to configure RSA SecureId 130 Appliance to integrate with Active Directory

How to configure RSA SecureId 130 Appliance to integrate with Active Directory

In this lab we will configure the RSA SecureID 130 appliance to integrate with AD and allow users to login using their tokens to AD, here are the steps to setup the appliance:

Setting up the Device:

the RSA appliance can be setup either as primary or secondary, the primary mode if either standalone or used in conjunction with the secondary one to provide HA, in our setup we will setup the primary device.

setting up the device is fairly simple, connect the device to the network, it comes pre-set with the IP, you will connect to that IP and set it up:


the wizard walks you through the initial setup wizard, where you import license file that came with the appliance, set the date and time, set the OS password, set the superadmin password, configure networking, after that it will take around 10 minutes to setup the device and reboot to start with the new configuration.

once rebooted, you can login to the operations console, you can access it using any web browser and browse to: :7072/operations-console">https://<IP Address>:7072/operations-console


once you login and to integrate with AD, you need to configure identity sources, to do so go to Manage Identity Sources .


Click on add new identity source


the add new identity source wizard opens, and it allows you to add your identity source, in our case we are using Microsoft Active Directory, enter the AD information including a dedicated username and password to connect and manage AD (in this lab I am using the administrator account please make sure to use a dedicated account in production environment), and click on test connection to verify your settings.


once successfully, you will be prompted with map wizard, this wizard will allow you to map AD attributes to AD (make sure not to include user base DN or Group base DN if you are adding a global catalog) confirm the attribute mapping and click next


now you will have your identity source configured


now you will login to the security console, and configure the realm, RSA(12).png

now go to Realm management and create a new one for the AD or choose edit and include AD in the existing realm


now from the security console, you can go for token management and search for your tokens that you have imported you will find them in the console


now you can search for a user and assign the token to him


the final step is to install the RSA client on the machine the user will login (local machine or XenApp Server for example), once the client installed it will disable the AD password login and will require the user to login using the token, these settings can be set using GPO or registry.

Note: for some reasons the latest version of the client didn’t work with me so I used the previous version which worked great, but it requires registry editing to enforce RSA login GINA.

hope that this quick guide helped you out.

  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: