RSA SecurID Single Sign-On (SSO) login for Magento [SAML] can be achieved by using our Magento SAML SP Single Sign-On (SSO) plugin.
Our SSO solution will make Magento SAML 2.0 compliant Service Provider establishing trust between the Magento site and RSA SecurID to securely authenticate and login users to the Magento site. Our Magento Single Sign-On (SSO) solution helps to
secure Magento sites behind the SSO login so that users are authenticated using their RSA SecurID login credentials. Seamless support for advanced SSO features like Attribute / Custom Mapping, Role Mapping etc.
SAML allows information to be exchanged between Service Providers and Identity Providers; SAML is the integration of Service Providers and Identity Providers. When a user attempts to log in, your Service provider delivers SAML assertions to Identity Provider, which contain information about the user. The assertion is received by Identity Provider, which validates it against your Service Provider settings before allowing the user access to your org.
Here we will go through a guide to configure SAML Single Sign-On SSO login between Magento site and RSA SecurID by considering RSA SecurID as IdP (Identity Provider) and Magento as SP (Service Provider). Our SSO plugin
provides Unlimited user authentications from RSA SecurID. To know more about other features we provide in you Magento SAML Single Sign-On (SSO) plugin, you can click here.
Steps to configure RSA SecurID SAML Single Sign-On (SSO) Login into Magento SAML SP
1. Setup RSA SecurID as IdP (Identity Provider)
Follow the steps below to configure RSA SecurID as IdP for Magento
Configure RSA SecurID as IdP
In the Magento SAML SP SSO plugin, navigate to Service Provider Metadata tab. In this tab you will find the SP metadata such as SP Entity ID and ACS (AssertionConsumerService) URL which are required to configure RSA SecurID as the Identity Provider.
Login to RSA SecurID Access (Cloud Console) as Admin.
In the top navigation menu, click on Applications → Application Catalog.
Click Create From Template button on the top right corner.
Click on Select Button next to the SAML Direct, in the Choose Connector Template page.
Fill the required information in the Basic Information .
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.
Now click on the Next Step button.
Click on Import Metadata button.
Upload the miniOrange plugin’s metadata file. You can download the plugin's metadata file from the Service Provider Metadata tab of the plugin.
Verify the configured URLs and clicks on the Save button on the top right corner of Import SAML Metadata window page.
Check if extension metadata is imported successfully.
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 as Connection URL or you can leave it blank if IDP-initiated is selected.
Binding Method for SAML Request: POST
Signed [a checkbox]: Uncheck (Note: The free version of WP SAML SSO Plugin does not support signed SAML requests. If you are using the paid versions of the plugin, you can send signed SAML requests)
SAML Identity Provider (Issuer)
Identity Provider URL: Note this value, it will be used as the SAML Login URL to configure the plugin.
Issuer Entity ID: Default (Note: This is the IdP Entity ID or Issuer used to configure in the plugin)
SAML Response Signature: Upload the private key and the certificate which will be used to sign the SAML Response or you can generate new key pair by clicking on the Generate Cert Bundle button.
Include Certificate in Outgoing Assertion: Enable (Optional)
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 Metadata tab of the miniOrange SAML plugin and update the URL here.
Configure NameID information that identifies the user who is generating the SAML Assertion.
Configure additional user information to be sent to the Application in the SAML Response. For example, username, email, display name, groups etc.
Now click on Next Step button.
Select the access policy as Allow all Authenticated Users and click on Next Step button.
Configure application display settings for RSA end users like app icon etc.
Now click on Save and Finish button to save the settings.
Now, from the top navigation bar, click Applications My Applications.
Find the app that you have configured. Click on down arrow besides the app's name and click on Export Metadata.
Keep the metadata handy, it will be required to configure miniOrange plugin.
Finally, click on Publish Changes button in the top left corner of the RSA Admin Console to publish this app configuration.
You have successfully configured RSA SecurID as SAML IdP (Identity Provider) for achieving RSA SecurID SSO login into your magento Site.
2. Configure Magento as SP (Service Provider)
Copy SAML Entity ID, SAML Single-Sign-On Endpoint URL and x.509 certificate from Federation Metadata document and paste it in IdP Entity ID or Issuer, Single Sign-on Service URL, x.509 Certificate fields respectively in the plugin.
IdP Entity ID or Issuer
SAML Entity ID in the Federation Metadata document
Single Sign-On Service URL
SAML Single-Sign-On Endpoint URL in the Federation Metadata document
x.509 Certificate in the Federation Metadata document
Click on Save button to save all your settings.
To check if your Magento as SP is configured correctly, click the Test Configuration button.
3. Sign-In Settings
Navigate to Sign-in Settings tab. Here you find the option the enable the login link on Admin*/Customer Login Page (*Admin SSO is available in the premium versions)
If you want to initate SSO from any page you can also use the SSO link provided in the extension.
The Premium extension also provides you the the feature to auto redirect your user to the IdP Login Page if the user is not already logged in.
4. Customer / Admin SSO
Customer Single Sign-On (Customer SSO)
Admin Single Sign-On (Admin SSO)
Go to customer login page and you will see the SSO button on your frontend. Click on the button and test the SSO.
You will be sucessfully logged in into Magento.
Visit your admin login page and you will see the SSO button on your admin page. Click on the button to initate SSO as an admin.
After sucessfully logged into magento as admin you will be redirect to magento backend dashboard.
Attribute Mapping / Custom Attribute Mapping(Optional). *This is Premium feature.
1.1: Attribute Mapping (Optional).
Attributes are user details that are stored in your Identity Provider.
Attribute Mapping helps you to get user attributes from your Identity Provider (IdP) and map them to Magento user attributes like firstname, lastname etc.
While auto registering the users in your Magento site these attributes will automatically get mapped to your Magento user details.
Only NameID can be mapped to Magento's Email and Username characteristics with the free plugin. Multiple user attributes from the IdP, on the other hand, can be mapped to Magento attributes in the premium version of the plugin. You can map custom attributes that you've added to your IdP in addition to the default attributes.
When a user performs SSO, the NameID value sent by the IdP will get mapped to the email and the username of the Magento user.
Name of the username attribute from IdP (Keep NameID by default)
Name of the email attribute from IdP (Keep NameID by default)
Name of the Role attribute from Identity Provider (IdP)
You can check the Test Configuration Results under Service Provider Setup tab to get a better idea of which values to map here.
1.2: Custom Attribute Mapping (Optional). *This is Premium feature.
Enter your table name in Table field.
Enter attribute name as your column name (in the respective table)
Click on Add button for adding custom magento attribute and map the respective field with the attribute receiving from your identity provider
Click on save button for saving the configuration.
You can also delete the configuration by entering the name in attribute name field and then click on delete button.
Role Mapping (Optional). *This is Premium feature.
You can specify a default role in the free plugin that will be allocated to all non-admin users when they conduct SSO.
Go to Attribute/Role mapping tab and navigate to Role Mapping section.
Select the Default Role and click on the Save button.
In this Guide, you have successfully configured RSA SecurID SAML Single Sign-On (RSA SecurID SSO Login) choosing RSA SecurID as IdP and Magento as SP using Magento SAML Sigle Sign-On (SSO) Login plugin .This solution ensures that you
are ready to roll out secure access to your Magento site using RSA SecurID login credentials within minutes.
If you dont hear from us within 24 hours, please feel free to send a follow up email to email@example.com
This privacy statement applies to miniorange websites describing how we handle the personal
When you visit any website, it may store or retrieve the information on your browser, mostly in the
form of the cookies. This information might be about you, your preferences or your device and is
mostly used to make the site work as you expect it to. The information does not directly identify
you, but it can give you a more personalized web experience.
Click on the category headings to check how we handle the cookies.
Strictly Necessary Cookies
Necessary cookies help make a website fully usable by enabling the basic functions like site
navigation, logging in, filling forms, etc. The cookies used for the functionality do not store any
personal identifiable information. However, some parts of the website will not work properly without
These cookies only collect aggregated information about the traffic of the website including -
visitors, sources, page clicks and views, etc. This allows us to know more about our most and least
popular pages along with users' interaction on the actionable elements and hence letting us improve
the performance of our website as well as our services.