Gina Salvalzo, RSA Partner Engineering
Last Modified: January 22, 2019
When integrated ServiceNow end users must authenticate with RSA SecurID Access to sign in. ServiceNow can integrate using SAML SSO Agent or Relying Party. ServiceNow does support JIT (just in time) user provisioning.
SSO Agent integrations use SAML 2.0 technologies to direct users’ web browsers to RSA SecurID Access for authentication. SSO Agents also provide Single Sign-On to other applications using the RSA Application Portal.
Relying Party integrations use SAML 2.0 to direct users’ web browsers to RSA SecurID Access for authentication.
This section shows all of the supported features by integration type and by RSA SecurID Access component. Use this information to determine which integration type and which RSA SecurID Access component your deployment will use. The next section in this guide contains the instruction steps for how to integrate RSA SecurID Access with ServiceNow using each integration type.
ServiceNow integration with RSA Cloud Authentication Service
ServiceNow integration with RSA Authentication Manager
|On Demand Authentication||-||-||-|
|- ||Not supported|
|n/t||Not yet tested or documented, but may be possible.|
This section contains links to the sections that contain instruction steps that show how to integrate ServiceNow with RSA SecurID Access using all of the integration types.
This document is not intended to suggest optimum installations or configurations. It is assumed that the reader has both working knowledge of all products involved, and the ability to perform the tasks outlined in this section. Administrators should have access to the product documentation for all products in order to install the required components. All RSA SecurID Access and ServiceNow components must be installed and working prior to the integration.
No known issues.