Cato Networks - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide
This article describes how to integrate RSA Cloud Authentication Service (CAS) with Cato Networks using OIDC.
Configure CAS
Perform these steps to configure CAS as Relying Party to Cato Networks.
Procedure
- Sign in to your RSA Cloud Administration Console.
- On the Access > My Page, enable Applications and click Save.
- Click Access > OIDC Settings.
- Add the email claim as shown in the following image and click New Claim.
- On the Scopes page, specify the following values and click Save Settings.
- Openid
- Profile
- Click Applications > Applications.
- Click Create From Template.
- Click Select for OIDC.
- Name your application and click Next Step.
- On the Authentication page, click Next Step.
- Add the Connection URL and Redirect URLs by copying them from Configuring RSA SSO (EA).
- In the Allow CORS Authentication section, enable the Participate in Unified Logout and Include Session Identifier toggle buttons.
- Copy the Relying Party Logout URLs from Configuring RSA SSO (EA) and click Next Step.
- On the Portal Display page, add Application Tooltip as required.
- Click Save and Finish and click Publish Changes.
After publishing, your application is now enabled for SSO.
Configure Cato Networks
Perform the following steps to configure Cato Networks.
Procedure
- Log in to Cato Networks with admin credentials.
- Go to the Access tab, and then choose Single Sign On.
- Click New.
- Choose RSA as the Identity Provider, name the new configuration, and make sure it is enabled and marked as Default.
- In the RSA Cloud Administration Console, go to the Connection Profile page of the application created.
- Copy the Authorization Server Issuer URL and use it as the Well-known URL.
- Add the following suffix: well-known/openid-configuration to the Well-known URL.
- Scroll down and copy the Client ID and Client Secret, and use them here.
RSA SSO is now configured and is the default SSO provider.
- Configure how RSA SSO will be used in your account.
The configuration is complete.
Related Articles
Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide 641Number of Views Microsoft Entra ID External MFA - RSA Ready Implementation Guide 629Number of Views Microsoft Entra ID Custom Controls - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide 214Number of Views Cato Networks - RSA Ready Implementation Guide 1Number of Views Palo Alto NGFW Global Protect - SAML Relying Party Configuration - RSA Ready Implementation Guide 130Number of Views
Trending Articles
RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows Customizing TLS Protocol Version RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA Release Notes for RSA Authentication Manager 8.8
Don't see what you're looking for?