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. This document is not intended to suggest optimum installations or configurations. First configure the integration type (RADIUS) then configure the use case ( Policy Sets). This section contains links to the sections that contain instruction steps that show how to integrate Cisco ISE with RSA SecurID Access using all of the integration types and also how to apply them to each supported use case. Not yet tested or documented, but may be possible Cisco ISE Integration with RSA Cloud Authentication ServiceĬisco ISE Integration with RSA Authentication Manager The next section in this guide contains the instruction steps for how to integrate RSA SecurID Access with Cisco ISE using each integration type. Use this information to determine which integration type and which RSA component your deployment will use. This section shows all the supported features by integration type and by RSA SecurID Access component. Authentication agents are simple to configure and support the highest rate of authentications. Primary authentication is configurable, and relying party can be a good choice for adding additional authentication (only) to existing deployments.Īuthentication Agent integrations use an embedded RSA agent to provide RSA SecurID and Authenticate OTP authentication methods within the partner’s application. Relying Party integrations use SAML 2.0 to direct users’ web browsers to the RSA Cloud Authentication Service for authentication. SSO provides Single Sign-On using the IDR My Applications/My Page Portal. SSO integrations use SAML 2.0 technologies to direct users’ web browsers to Cloud Authentication Service for authentication. RADIUS also provides support for most RSA SecurID Access authentication methods and flows. RADIUS integrations provide a text-driven interface for RSA SecurID Access within the partner application. Admin Access can be integrated with RSA SecurID Access using RADIUS or Authentication Agent. My Device Portal can be integrated with RSA SecurID Access using SAML SSO Agent or Relying Party.Īdmin Access - When integrated, users must authenticate with RSA SecurID Access in order to login to Cisco ISE administrative interface. My Device Portal - When integrated, users must authenticate with RSA SecurID Access in order to login to the My Device Portal. Guest Access Portal can be integrated with RSA SecurID Access using RADIUS, SAML SSO Agent, Relying Party, and Authentication Agent. Guest Access Portal - When integrated, users must authenticate with RSA SecurID Access in order to login to the Guest Access Portal. Policy Sets can be integrated with RSA SecurID Access using RADIUS or Authentication Agent. Policy Sets - When integrated, users must authenticate with RSA SecurID Access in order gain the access defined in the policy set. Use CasesĬisco ISE can be integrated with RSA SecurID to provide RSA SecurID authentication using SAML, Native SecurID, or RADIUS. Use this information to determine which use case and integration type your deployment will employ. This section describes Cisco ISE integration with RSA SecurID (or ID Plus).
0 Comments
Leave a Reply. |