SmartBear Bugsnag - SAML Relying Party Configuration - SecurID Access Implementation Guide
This section describes how to integrate SecurID Access with Bugsnag using Relying Party. Relying party uses SAML 2.0 to integrate SecurID Access as a SAML Identity Provider (IdP) to Bugsnag 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 Bugsnag .
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. Bugsnag 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.
-
Enter the Assertion Consumer Service (ACS) . Enter the value for the SAML Endpoint URL found in the Bugsnag configuration. This is based on your Bugsnag instance. The URL is in the form of https://app.bugsnag.com/user/sign_in/saml/<INSTANCE/acs. For example, https://app.bugsnag.com/user/sign_in/saml/rsamytest-3/acs.
-
Enter the Service Provider Entity ID. Enter the value for the EntityID forBugsnag. This is https://app.bugsnag.com.
-
Uncheck SP signs SAML Requests.
-
Click on Download Certificate. This will be used below in the Bugsnag configuration.
-
Click on Choose File and upload the certificate just downloaded. This same certificate may be used in the Bugsnag configuration below.
-
Open Advanced Configuration section
-
For Identifier Type Email Address choose mail for the Property.
-
Note the Identity Provider Entity ID field . For Example :https://rsa-inst-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 for Bugsnag configuration.
-
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 Bugsnag
Perform these steps to integrate Bugsnag with SecurID Access as a Relying Party SAML SP.
Procedure
-
Sign into Bugsnag and select Organization.
-
Goto Single sign-on.
-
Note the SAML Endpoint URL this information is used for the SecurID CAS configuration.
-
Based on how you saved off the IdP Metatdata from SecurID Access configuration. Either choose URL and paste the URL to the metatdata file or choose XML and load the XML from the metadata file.
-
Uncheck Auto-provision collaborators.
-
Select Enable SSO.
-
Click on Save.
Configuration is complete.
Next Step: See main page for more certification information.
Related Articles
Snowflake-integration-configuration-relying-party 2Number of Views How to use any client certificate as an Administrator in another KCA installation? 6Number of Views Start DB Logging button disabled in RSA Identity Governance & Lifecycle 171Number of Views Oracle INS-41812 OSDBA and OSASM are the same OS group warning during RSA Identity Governance & Lifecycle installation 38Number of Views How to deploy custom plugins in RSA Identity Governance and Lifecycle 103Number 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