Please note that you need to have a valid subscription from RSA in order to use this connector along with WSO2 Identity Server. Also, please note that this connector has been released for WSO2 Identity Server 5.1.0 only.
This page provides instructions on how to configure the RSA SecurID authenticator and the WSO2 Identity Server using a sample app to demonstrate authentication. You can find more information in the following sections.
Configuring the RSA Authentication Manager
RSA Authentication Manager 8.1 supports a VMware virtual appliance, Hyper-V virtual appliance, and the hardware appliance. The same functionality is provided by each type of appliance. See the setup and configuration guide for RSA Authentication Manager 8.1 for more information on setting this up.
Once you complete all the required configurations you can access the following consoles using the credentials that you provided in the configuration.
- Security Console: https://<Fully Qualified Domain Name>/sc
- Operational Console: https://<Fully Qualified Domain Name>/oc
- Self Service Console: https://<Fully Qualified Domain Name>/ssc
Configuring the NTP Server on RSA Authentication Manager operational console
The NTP server is responsible for time. Set up your NTP server for your region and make sure the time setting is accurate. To set the time, follow the steps below.
- Log in to the RSA Authentication Manager Operational Console (https://<Fully Qualified Domain Name>/oc) with your operation console credentials. This was set when you performed the RSA Authentication Manager configurations.
- Navigate to the Administration menu and select Date and Time.
- Set up your regional NTP server as shown in the following screen, but do this for your region.
Adding a user to the internal database of RSA Authentication Manager
To enroll the user into the RSA Authentication Manager, you must log into the security console (https://<Fully Qualified Domain Name>/oc) with your security console credentials. See the following video for more information on how to do this.
Importing token records
Token records are unique records used to identify each token in RSA. To activate a token record you must import the token record. See the following video, which guides you through the steps on how to import the token records to the RSA Authentication Manager Security Console.
Assigning the token to the user
Once the token records are imported and the users are added, you are able to assign either software tokens or hardware tokens to the users. See the following video, which guides you through the process of assigning a token to the registered user.
Self-enrollment of users and setting or resetting the PIN
The RSA Self-service Console provides the option to create/reset the password for users using their RSA user ID and their tokens. If the users log in for the first time, they must log in to the RSA Self-service Console and create a PIN for themselves.
RSA Self-Service Console URL: https://<FQDN-of-RSA-Authentication-Manager>/ssc
Configuring the RSA custom agent
If you are want to configure an RSA Authentication custom agent, you must generate the RSA Authentication Manager configuration file. See the following video for instructions on how to generate the configuration file.
Once you have generated the Authentication Manager configuration file, create a file called rsa.properties and add the following configurations to it. You must set the paths of each of the required files in this configuration.
Set the file path of the rsa.properties file you created in the
<IS_HOME>/repository/conf/identity/application-authentication.xmlfile as follows.
Deploying RSA SecurID Authenticator artifacts
The artifacts can be obtained from the store for this authenticator.
- Place the
securidauthenticationendpoint.warfile into the
org.wso2.carbon.extension.identity.authenticator.securid.connector-1.0.1.jarfile into the
If you want to upgrade the RSA SecurID Authenticator in your existing IS pack, please refer upgrade instructions.
- Obtain the
cryptoj.jarfrom RSA or RSA Support, and place the .jar files in the
Add a claim mapping for RSA user id
- Navigate to the Identity section under the Main tab of the management console and click Add under the claims dialect.
- Add a new claim for RSA user id.
Deploying travelocity.com sample app
The next step is to deploy the travelocity.com sample app in order to use it in this scenario.
See deploying travelocity.com sample app for instructions on how to do this.
Configuring the service provider
The next step is to configure the service provider.
- Return to the management console. In the Service Providers section under the Main tab, click Add.
- Since you are using travelocity as the sample, enter travelocity.com in the Service Provider Name text box and click Register.
- Now set the configuration as follows:
Do the following configurations.
- Issuer: travelocity.com
- Assertion Consumer URL: http://localhost:8080/travelocity.com/home.jsp
Select the following check-boxes:
- Enable Response Signing.
- Enable Single Logout.
- Enable Attribute Profile.
- Include Attributes in the Response Always.
- Issuer: travelocity.com
- Click Update to save the changes. Now you will be sent back to the Service Providers page.
- Go to the Local and Outbound Authentication Configuration section.
- Select the Advanced configuration radio button option.
- Add the basic authentication as the first step and RSASecurID authentication as the second step and click Update to save the changes.
Testing the sample
To test the sample you need to add the RSA user ID in the WSO2 Identity Server claim.
- Go to the following URL:
- Click the link to log in with SAML from WSO2 Identity Server. The basic authentication page appears. Use your WSO2 Identity Server credentials to log in.
- If the basic authentication succeeds, you are directed to RSA SecurID authentication page.
- Enter the PIN and TOKEN, where TOKEN is shown in the keyfobs or in your mobile device RSA applications.
- If the authentication is successful, you are redirected to the home page of travelocity.com app