Moodle SAML Single Sign-On (SSO) using RSA SecurID as IdP | RSA SecurID SSO Login

 Configure RSA SecurID as IdP

• In the Plugins tab scroll to Service Provider Metadata section you can find the SP metadata such as SP Entity-ID and ACS (AssertionConsumerService) URL which are required to configure 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.



 Connection Profile

• 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 plugin metadata is imported successfully.




 Initiate SAML Workflow

• Connection URL: Enter the URL from where the SSO request will be generated i.e. the URL where you want to redirect after successful Single Sign On.
• Select SP-Initiated, since the SSO is invoked from the Application side.
• Binding Method for SAML Request: POST
  (Note: The free version of SAML 2.0 SSO Plugin supports only POST binding for SAML Requests.)
• Signed [a checkbox]: Uncheck
  (Note: The free version of SAML 2.0 SSO Plugin doesnot 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)


 Service Provider

• 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.

 User Identity

• Configure NameID information that identifies the user who is generating the SAML Assertion.


 Advanced Configuration: Attribute Extention (Optional)

• 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.



 User Access

• Select the access policy as Allow all Authenticated Users and click on Next Step button.




 Portal Display

• 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.