OneDesk - SAML Relying Party Configuration - SecurID Access Implementation Guide
This section describes how to integrate SecurID Access with OneDesk using Relying Party. Relying party uses SAML 2.0 to integrate SecurID Access as a SAML Identity Provider (IdP) to OneDesk 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 OneDesk .
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. OneDesk 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 ACS value obtained from the OneDesk Service Provider Metadata file. For example, https://app.onedesk.com/sso/saml/SSO/alias/onedesk.com_snutest.
-
For the Service Provider Entity ID enter the Entity ID value obtained from the OneDesk Service Provider Metadata file. For example, onedesk.com_snutest.
-
Uncheck SP signs SAML Requests.
-
Check IdP signs assertion within response.
-
Click on Download Certificate. This may be used below in the OneDesk configuration.
-
Open Advanced Configuration section.
-
Ensure Email Address is set to the mail property.
-
Under Attribute Extension add the following three attributes.
-
FirstName set Property to givenName.
-
LastName set Property to sn.
-
EmailAddress set Property to mail.
-
Note property values may be different for your SecurID Access 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 IdP metadata information. This file will be uploaded in the OneDesk 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 OneDesk
Perform these steps to integrate OneDesk with SecurID Access as a Relying Party SAML SP.
Procedure
-
Login into OneDesk.
-
Browse to Administration > Integrations > Single Sign On and enable.
-
Click on Upload Metadata File then Choose File and loading the SecurID Metadata file downloaded above.
-
Under Advanced Settings, ensure that the Email, First Name, and Last Name Attributes names match those configured in the SecurID Access Configuration.
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… 502Number of Views GoToMeeting - SAML Relying Party Configuration - RSA Ready Implementation Guide 14Number of Views Microsoft Office 365 - SAML Relying Party Configuration - RSA Ready Implementation Guide 243Number 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
Trending Articles
Downloading RSA Authentication Manager license files or RSA Software token seed records Unable to login to RSA Authentication Manager Security Console as super admin RSA Authentication Manager 8.9 Release Notes (January 2026) How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Connection fails to Cloud Authentication Service when connecting through a proxy server from RSA Authentication Manager to…