IBM Resilient - SAML Relying Party Configuration - RSA Ready Implementation Guide
Configure RSA Cloud Authentication Service
Perform these steps to configure RSA Cloud Authentication Service as Relying Party to IBM Resilient.Procedure
- Sign in to RSA Cloud Administration Console.
- Click Authentication Clients > Relying Parties.
- On the Relying Party Catalog page, click Add a Relying Party and click Add for Service Provider SAML.
- On the Basic Information page, enter the name for the application in the Name field and click Next Step.
- On the Authentication page, choose SecurID manages all authentication.
- Select a Primary Authentication Method and Access Policy as required and click Next Step.
- For providing Service Provider details:
- Select Import Metadata and click Choose File.
- Select the file that is downloaded from the Service Provider.
Refer to the Configure IBM Resilient section to download the metadata.
- Review the ACS URL and Service Provider Entity ID values that are auto-filled.
- Retain the SP signs SAML requests and Encrypt Assertion checkbox selections.
- In the SAML Response Protection section, choose IdP signs assertion within response.
- Download the certificate by clicking Download Certificate.
- Click Show Advanced Configuration.
- Under the User Identity section, configure Identifier Type and Property. For example, Identifier Type: Auto Detect and Property: Auto Detect.
- Under the Attribute Extension section, add the attributes as shown in the following figure.
- Click Save and Finish.
- On the My Relying Parties page, click the Edit drop-down and select the Metadata option to download the metadata.
- Click Publish Changes. Your application is now enabled for SSO.
Configure IBM Resilient
Perform these steps to configure IBM Resilient.Procedure
- Log on to the IBM Resilient terminal using the administrator credentials.
- Create a SAML federation by running the following command - sudo resutil samledit -alias <alias_name> -certfile <certfile.pem> -org "<org_name>" -createusers -loginurl <idp_login_url>
- alias_name - Provide a unique name for creating a SAML federation.
- certfile.pem - Provide the downloaded certificate from RSA.
- org_name - Provide the IBM Resilient SOAR platform organization name.
- idp_login_url – The SingleSignOnService value that can be obtained from the metadata file downloaded from RSA.
The preceding command also prints the SAML federation details to the console and writes the following files. <alias>-metadata.xml - SAML XML metadata that can be imported into RSA to complete the configuration.
<alias>-sp-cert.pem - Service Provider certificate that was automatically generated.
- Copy <alias>-metadata.xml SAML metadata file by running the following command - cat <alias>-metadata.xml. Copy and save the .xml file that is used to configure RSA.
- After the SAML in the Identity Provider is configured, check the SAML configuration by running the following command.
Example:
The configuration is complete.
Return to IBM Resilient - RSA Ready Implementation Guide.
Related Articles
Microsoft Office 365 - SAML Relying Party Configuration - RSA Ready Implementation Guide 250Number of Views CyberArk Password Vault Web Access - SAML Relying Party Configuration - RSA Ready Implementation Guide 45Number of Views Microsoft Entra ID External Authentication Methods (EAM) - Relying Party Configuration Using OIDC - RSA Ready Implementati… 509Number of Views Palo Alto NGFW Global Protect - SAML Relying Party Configuration - RSA Ready Implementation Guide 110Number of Views Okta - SAML Relying Party Configuration - RSA Ready Implementation Guide 45Number of Views
Trending Articles
Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Governance & Lifecycle 8.0.0 Administrators Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory
Don't see what you're looking for?