This article explains how to configure PingFederate as the Single Sign-On (SSO) provider for SDP users.
Configuring SSO for your account simplifies authentication and enhances the user experience. With SSO configured for your account, SDP users are able to log in to the Client and authenticate with their SSO credentials and do not a different set of dedicated credentials. To use SSO in your Cato account, you can configure your IdP as an SSO provider in the Cato Management Application.
Configuring PingFederate as an SSO provider leverages the federation between PingFederate and Azure AD.
-
On premise PingFederate deployment
-
Active Azure subscription
-
Active Directory domain with verified ownership to be federated
-
CA signed certificate for the federated domain name
-
Publicly accessible PingFederate Runtime Engine nodes (for Azure AD redirect to PingFederate during SSO)
Before configuring PingFederate as an SSO provider for Cato, you must first integrate your PingFederate account to your Azure AD tenant. For more information and instructions, see the PingFederate documentation. Once this integration is complete, enable Active Directory synchronization with Microsoft Azure Active Directory Connect, then configure Azure as the Identity Provider in the Cato Management Application.
To configure PingFederate as the SSO provider for your account:
-
Download and install Microsoft Azure Active Directory Connect.
-
On the User Sign-in screen, choose Federation with PingFederation and click Next.
-
On the Azure AD domain screen, select the domain you are configuring the federation for and click Next.
-
On the PingFederate Settings screen, enter your PingFederate publicly accessible server URL.
-
Click Next and then Finish.
-
In a new tab or window, open the Cato Management Application.
-
Configure Azure SSO for your account. For more information, see Configuring Azure SSO for Your Account.
Comments
0 comments
Article is closed for comments.