Pingboard - SAML Relying Party Configuration - SecurID Access Implementation Guide
This section describes how to integrate SecurID Access with Pingboard using Relying Party. Relying party uses SAML 2.0 to integrate SecurID Access as a SAML Identity Provider (IdP) to Pingboard 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 Pingboard .
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. Pingboard 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 a dummy value for now. For example, https://dummy.com. This will be populated later with SP metadata xml file.
-
Enter the Service Provider Entity ID. Enter a dummy value for now. For example, dummy. This will be populated later with SP metadata xml file.
-
-
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 to be used in the Pingboard configuration below. When IdP metata data is loaded into the Pingboard configuration then proceed further.
-
Click Edit on the newly created Relying Party configuration to load the Pingboard SP metadata information.
-
Go to Connection Profile section.
-
Click on Import Metadata and click on Choose File to load the SP Metadata file from Pingboard. This will populate the Service Provider Metadata information. You can also configure it manually with the information from the SP Metadata.
-
Click on Save and Finish.
-
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 Pingboard
Perform these steps to integrate Pingboard with SecurID Access as a Relying Party SAML SP.
Procedure
-
Sign into Pingboard and Click on Admin tab.
-
Click on Add-ons.
-
Select Custom SSO.
-
For Dashboard IDP Metadata copy and paste the contents exported IDP Metadata saved above during SecurID CAS configuration.
-
When the IDP Metadata is submitted, Pingboard will provide the URL to SP metadata xml file. Save off the metatdata into an xml file which will be used to further configuration SecurID Access configuration. Or use the information to manually configure SecurID.
-
Save changes.
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 Evernote - SAML Relying Party Configuration - RSA Ready Implementation Guide 7Number of Views PingFederate - Relying Party Configuration Using SAML - RSA Ready Implementation Guide 196Number 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