This article explains how to configure Keycloak as the only Single Sign-On (SSO) provider for SDP users and Cato Management Application (CMA) admins.
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.
You can configure Keycloak as the SSO provider to centralize authentication for both CMA admins and remote users connecting with the Cato Client. This integration improves account security and simplifies identity management by enforcing login through Keycloak credentials.
Make sure that the email address for each user and admin in Cato matches the corresponding email in Keycloak.
Once SSO is enabled, admins must authenticate through Keycloak to access the CMA, and both admins and users must authenticate through Keycloak to connect with the Cato Client.
Follow these steps to configure Keycloak as an SSO provider:
-
Add Cato as a Keycloak client in your Keycloak admin console
-
Enter the details of your Keycloak Host in the CMA
In the Keycloak admin console, add Cato as a client. Allowlist the Cato URIs as part of configuring Cato as a client. You will need these values for the CMA in step 2:
-
client ID
-
client secret
This procedure refers to the Keycloak console, which is subject to change. To read the latest Keycloak documentation, see Managing Resource Servers.
To add Cato as a Keycloak client:
-
In Keycloak, go to Clients > Create Client.
-
In the General settings tab, enter the basic settings, including a client ID. You will need the client ID to integrate with Cato later.
-
In the Capability config tab, make sure Client authentication is enabled.
-
In the Login settings tab, enter the following Cato URIs in Valid redirect URIs:
-
https://sso.via.catonetworks.com/auth_results
-
https://sso.ias.catonetworks.com/auth_results
-
https://sso.proxy.catonetworks.com/auth_results
-
https://169.254.255.254/auth_results
-
https://auth.catonetworks.com/oauth2/broker/code/keycloak
-
https://auth.us1.catonetworks.com/oauth2/broker/code/keycloak
-
https://auth.catonetworks.com/endsession/*
-
https://auth.us1.catonetworks.com/endsession/*
-
-
Click Save to create the Keycloak client.
-
Go to the Client area and click the client you just created.
-
Go to the Credentials tab and copy the Client Secret. You will need this value when you create the SSO provider in the CMA.
In the CMA, enter the details for your Keycloak client you created in the previous step:
-
Keycloak URL
-
Client ID
-
Client secret
The value for the Keycloak URL is the beginning of the URL until the end of the Realm name, without HTTPS.
For example, if the URL you use to get to Keycloak is https://keycloak.example.com/realms/myRealm/.well-known/openid-configuration, you would enter keycloak.example.com/realms/myRealm as your Keycloak URL.
Cato supports using multiple IdPs for SSO for your account. Only the default SSO provider is used for CMA admins, make sure to define Keycloak as the Default authentication method.
To configure Keycloak as your SSO provider:
-
In the CMA, from the navigation menu, click Access > Single Sign On.
-
Click New.
-
From the Identity Provider drop-down menu, select Keycloak.
-
Enter a Name to identify this integration.
-
Enter your Keycloak URL without the protocol prefix and only up until your realm name.
-
Enter the Client ID and Client Secret that were created in step 1.
-
Enable the Default toggle to use Keycloak as the only SSO provider for CMA admins.
-
Click Apply.
0 comments
Article is closed for comments.