Cato Networks - RSA Ready Implementation Guide
a day ago

Certified: July 01, 2026

     

Solution Summary

This article describes the configuration steps involved in integrating Cato Networks with RSA Cloud Access Service (CAS) using OIDC.

        

Use Case

Cato Networks can be integrated with RSA using Relying Party. When integrated, users must authenticate with RSA to sign in to Cato Networks.  

         

Integration Types

Relying Party integration allows Cato Networks users’ web browsers to be automatically redirected to CAS for authentication. With Relying Party integration, CAS can manage either additional authentication only or both primary authentication (for example, user ID and password) and additional authentication, depending on the service provider's capability.

        

Supported Features

This section shows all the supported features by integration type and by RSA components. Use this information to determine which integration type and RSA component your deployment will use. The next section in this guide contains the instruction steps for how to integrate RSA with Cato Networks using each integration type.

       

Cato Networks Integration with CAS

Authentication MethodsRSA MFA API (REST)RADIUSRelying PartyMy Page SSO
ApproveUnsupportedNot testedSupportedUnsupported
Approve with Code Matching
Unsupported
Not tested
Unsupported
Unsupported
LDAP PasswordUnsupportedNot testedSupportedUnsupported
SecurID OTPUnsupportedNot testedSupportedUnsupported
Authenticate OTPUnsupportedNot testedSupportedUnsupported
Device BiometricsUnsupportedNot testedSupportedUnsupported
Device Biometrics with Code Matching
Unsupported
Not tested
Unsupported
Unsupported
SMS OTPUnsupportedNot testedSupportedUnsupported
Voice OTPUnsupportedNot testedSupportedUnsupported
FIDO Security KeyUnsupportedNot testedSupportedUnsupported
QR CodeUnsupportedNot testedSupportedUnsupported
Emergency Access CodeUnsupportedNot testedSupportedUnsupported

Note: CAS supports code matching for push notifications. Applications that do not support the code matching feature should not enable Strict Code Matching Enforcement. For more information, see Configure Session and Authentication Method Settings > Configure Code Matching Settings.      

     

Cato Networks Integration with RSA Authentication Manager (AM)

Authentication MethodsRSA MFA API (REST)RADIUSAuthentication Agent
RSA SecurIDUnsupportedNot testedUnsupported
On Demand AuthenticationUnsupportedNot testedUnsupported
Risk-Based AuthenticationUnsupportedNot testedUnsupported

            

Configuration Summary

This section contains instruction steps that show how to integrate Cato Networks with RSA 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 to install the required components.
All RSA and Cato Networks components must be installed and working prior to the integration.
This section of the guide includes links to the appropriate sections for configuring both sides for each use case.
    

Integration Configuration

CAS

                 

RSA Terminology Changes

The following table describes the differences in the terminologies used in the different versions of RSA products and components. 

Previous VersionNew VersionExamples/Comments
Cloud Authentication ServiceCloud Access Service
Token

OTP CredentialSecurID OTP Credential
AuthenticatorHardware Authenticator
Tokencode

OTPSecurID OTP, SMS OTP, Voice OTP
Access CodeEmergency Access Code
SecurID Authenticate appRSA Authenticator appRSA Authenticator app for iOS and Android, RSA Authenticator app for Windows
DeviceAuthenticatorRegister an authenticator
Company IDOrganization ID 
AccountCredential 
Device Serial NumberBinding ID 

         

Certification Details

CAS

Cato Networks

      

Known Issues

No Known issues.