Drupal RSA SecurID SSO setup will allow your user to login to your Drupal site using their RSA SecurID Credentials. The Drupal SAML module gives the ability to enable SAML Single Sign-On for Drupal. This module is compatible with all SAML Identity Providers. Here we will go through a guide to configure SAML SSO between Drupal and RSA SecurID. By the end of this guide, users from RSA SecurID should be able to login into the Drupal website.
If you have any doubts or queries, you can contact us at email@example.com. We will help you to configure the module.
Step 1:Setup RSA SecurID as Identity Provider
- Login to the RSA Secure ID as Super Admin.
- In the Administration Console, click Application → Application Catalog.
- Click Create From Template button on the top right corner.
- Next to the SAML Direct, click select in the Choose Connector Template page. The Add Connector wizard appears.
- Fill the required information in the Basic Information page on the Add Connector wizard.
- Name:- Name of the application for eg. miniOrange Plugin.
- Description (Optional):- Description for your application.
- Disabled [a checkbox] (optional): Select this only if you want to make this application unavailable to users. When disabled, the application appears in My Application but does not appear in the RSA application portal.
- Click Next Step button.
- Fill the required information in the Connection Profile page.
- Upload the miniOrange module metadata file and click on the Import Metadata button. You can download it from the Service Provider info tab of the module.
- Verify the configured URLs and clicks on the Save button on the top right corner of the pop-up window.
Initiate SAML Workflow
- Select SP-Initiated, if you want the SSO should be invoked from Application or select IDP-initiated, if you want the user should log in into RSA first and then access Application from his RSA Dashboard.
- Configure base URL of your Application or you can leave it blank if IDP-initiated is selected.
- Select Binding type: POST and Signed Checked.
SAML Identity Provider(Issuer)
- Upload the public and private key which will be used to signed SAML Response or you can generate new key pair by clicking on the Generate Cert Bundle button.
- (Optional) Enable checkbox for Include Certificate in Outgoing Assertion.
- Assertion Consumer Service URL and Audience URL should be preconfigured if you have uploaded plugin’s metadata in the Connection Profile section. If not, you can find the required URLs from Service Provider Info tab of the miniOrange SAML plugin and update the URL here.
- Configure NameID information that identifies the user on whose behalf the SAML Assertion is generated.
Advanced Configuration: Attribute Extention
- Configure additional user information to be sent to the Application in the SAML Response, for example, username, email, display name, groups etc.
Advanced Configuration: Uncommon Formatting SAML Response
Define application access in the User Access page.
Configure application display settings for RSA end users like app icon etc and save the settings
Now, In the Administration Console, click Application My Application.
Find the app that you have configured and click on Edit Export Metadata. Keep the metadata handy, it will require to configure miniOrange module.
Click on Publish Changes in the top left corner of the RSA Admin Console to publish this configuration and immediately activate it.
- Sign outgoing Assertion:- Assertion within Response.
- Encrypt Assertion (Optional): If checked, you need to load miniOrange module public certificate and you can download it from the Service Provider Info tab of the module.
- Unchecked Send encoded URL in Assertion.
- Checked include issuer NameID format and select NameID Format as Unspecified.
- Save the configuration and move to the next page i.e. User Access page.
Step 2: Configuring Drupal as Service Provider (SP)
If you don't find what you are looking for, please contact us at firstname.lastname@example.org or call us at +1 978 658 9387.