Aha! - SAML Relying Party Configuration - SecurID Access Implementation Guide
This section describes how to integrate SecurID Access with Aha! using Relying Party. Relying party uses SAML 2.0 to integrate SecurID Access as a SAML Identity Provider (IdP) to Aha! SAML Service Provider (SP).
Architecture Diagram
Configure SecurID Access Cloud Authentication Service
Perform these steps to configure SecurID Access Cloud Authentication Service(CAS) as a relying party SAML IdP to Aha! .
Procedure
-
Sign into the Cloud Administration Console and browse to Authentication Clients > Relying Parties and click Add a Relying Party. Then select Add for a SAML service provider.
-
On Basic Information page enter a Name for the application, ie. Aha! Then click on Next Step.
-
On Authentication page.
-
select the RSA SecurID Access manages all authentication.
-
Select the desired Primary Authentication Method from the dropdown list.
-
Select the desired policy from the Access Policy for Additional Authentication.
-
Click Next Step.
-
-
On Connection Profile page.
-
Under the Service Provider Metadata section.
-
For the Assertion Consumer Service (ACS) enter the SAML consumer URL from Aha! SP information in the SSO setup below. This URL is based on your instance of Aha!. For example, https://mytestinst.aha.io/auth/saml/callback.
-
For the Service Provider Entity ID enter the SAML entitity ID from Aha! SP information in the SSO setup below. This URL is based on your instance of Aha!. For example, https://mytestinst.aha.io/.
-
Uncheck SP signs SAML Requests.
-
Check IdP signs assertion within response.
-
Click on Download Certificate. This will be used below in the Aha! configuration.
-
Open Advanced Configuration section.
-
Ensure the Identifier Type is Email Address and the Property is set to mail, based on your configuration.
-
Note the Identity Provider Entity ID field . For Example :https://rsa-test-pe.auth-demo.securid.com/saml-fe/sso.
-
-
Click on Save and Finish.
-
Browse to Authentication Clients > Relying Parties .
-
Scroll down to the your newly created Relying party and click down arrow to Edit and choose View or Download IdP MetatData and save off the metadata information if desired.
-
Click on Publish Changes. Your application is now enabled for SSO. If you make any additional changes to the application configuration you will need to republish.
Configure Aha!
Perform these steps to integrate Aha! with SecurID Access as a Relying Party SAML SP.
Procedure
-
Login into your Aha! account.
-
Browse to Account > Security and single sign-on.
-
Select SAML 2.0 from Identity provider list.
-
Enter a Name for the Identity provider. For example, MySecurID.
-
For Configure using select Metadata file. Then Choose File and upload the saved metadata file from the SecurID configuration above.
-
Note the SAML consumer URL and SAML entitity ID. These will be used in the SecurID configuration above.
-
Click on Enable.
Configuration is complete.
Next Step: See main page for more certification information.
Related Articles
Microsoft Entra ID External Authentication Methods (EAM) - Relying Party Configuration Using OIDC - RSA Ready Implementati… 499Number of Views GoToMeeting - SAML Relying Party Configuration - RSA Ready Implementation Guide 14Number of Views Dropbox - SAML Relying Party Configuration - RSA Ready Implementation Guide 8Number of Views PingFederate - Relying Party Configuration Using SAML - RSA Ready Implementation Guide 196Number of Views Evernote - SAML Relying Party Configuration - RSA Ready Implementation Guide 7Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x