Configuring RSA SSO (EA)

This article explains how to configure RSA as the Single Sign-On (SSO) provider for users.

SSO relies on an encrypted token from Cato and your IdP to validate that the user is authenticated and allowed to connect to the network. For more details, see SSO Authentication for Users with Cato.

Note

Note: This is an Early Availability (EA) feature that is only available for limited release. For more information about enabling the feature, contact your Cato Networks representative or send an email to ea@catonetworks.com.

Overview

Configuring RSA as the SSO provider simplifies authentication and enhances user experience. When you enable SSO for the account, users can log in to the Client by authenticating with their SSO credentials and do not need a different set of dedicated credentials.

Configuring RSA as an SSO Provider

Follow these steps to configure RSA as an SSO provider:

Create an OIDC application in the RSA Administration Console
Configure the details in the Cato Management Application (CMA)
Configure how RSA is used in your account

Step 1: Creating an Application in the RSA Administration Console

In the RSA Administration Console, create an application and identify the following values to enter into the CMA:

Authorization Server Issuer URL
Client ID
Client Secret

To create an application:

Log in to your RSA Administration Console.
Navigate to Access > OIDC Settings.
Enter these details:
- Claim Name: email
- Source: Identity Source
- Property: mail
- Type: default
Click on the plus then Save Settings.
On the Scopes tab create these scopes:
- email
- openid
- profile
Click Save Settings.
On the Application tab, click Add an Application then click Create From Template.
Select OIDC.
Add a name for the application.
On the Connection Profile tab, add these details:
- Connection URL: https://sso.ias.catonetworks.com/auth_results
- Redirect URI:
- Client Authentication Method: CLIENT_SECRET_POST
- Scopes:
  - openID
  - profile
  - email
- Claims:
  - email
Copy and save the Authorization Server Issuer URL so it can be entered into the CMA.
Choose a Client ID and copy and save it so it can be entered into the CMA.
Under Authorization Code Flow, click Generate and copy and save the Client Secret so it can be entered into the CMA.
In the Allow CORS Authentication section, enable the Participate in Unified Logout and Include Session Identifier toggles.
In the Relying Party Logout URL field add: https://auth.sta.catonet.works/endsession
In the Logout Redirect URIs field, add: https://auth.sta.catonet.works/endsession/callback
On the Portal Display tab, click Save and Finish.
Navigate to Access > My Page.
Set the Applications toggle to Enabled.

Step 2: Configure RSA as an SSO Provider

In the CMA, enter the details for the RSA application you created in the previous step:

Authorization Server Issuer URL is the Well-Known URL
Client ID
Client secret

To configure RSA as an SSO provider:

In the CMA, from the navigation menu, click Access > Single Sign On.
Click New.
From the Identity Provider drop-down menu, select RSA.
Enter a Name to identify this integration.
(Optional) To configure RSA as your default SSO provider, enable the Default toggle. If you are configuring multiple Single Sign-On providers, see Configuring Multiple Identity Providers.
Enter the Well-Known URL and Client ID you created in Step 1.
Click Edit Client Secret and enter the value you created in Step 1.
Click Apply.

Step 3: Configure How RSA is Used in your Account

You can choose to allow users, Cato Management Application admins, or both to authenticate with SSO using RSA.

You can also configure how long the Cato authentication token is valid for. The Token validity settings define in Days or Hours the amount of time that users remain authenticated. Users that are logged in must re-authenticate when the duration you define in Days or Hours (since they last logged in) has been reached.

The Always Prompt options means that users must always authenticate to the Client.

To configure how RSA is used in your account:

On the Access > Single Sign On page, define which users can authenticate with SSO and if necessary, define the Token validity, Cookie type, and Duration settings.
Click Save.