Configuring SAML SSO with Lookout Secure Access
The Ping Identity and Lookout SAML integration supports service provider (SP) and identity provider (IdP) initiated single sign-on (SSO).
What it is
Lookout Cloud Security (Lookout SSE platform) is a data-centric cloud security solution that protects users from internet-based threats and protects data stored in cloud applications, private applications, and websites.
Lookout Cloud Security supports the following cloud security components:
- Lookout Secure Internet Access
-
Protection for web or non-web internet-based traffic.
- Lookout Secure Private Access
-
Protection for private application traffic.
- Lookout Secure Cloud Access
-
Protection for cloud application traffic.
Users must authenticate with your enterprise SSO provider during their initial access before accessing solutions such as Secure Internet Access and Secure Cloud Access. |
The Lookout Cloud Security platform leverages the user or user group context to enforce access and activity policies on cloud apps, private apps, and websites.
What you’ll need
-
Have a PingOne account. Learn more in Starting a PingOne trial.
-
Verify that you can sign on to the PingOne admin console. Learn more in Accessing the PingOne admin console.
-
Have a Lookout SSE platform account. To enroll in a Lookout SSE platform account, contact Lookout.
What you’ll do
To configure SAML SSO with Lookout Secure Access:
-
Gather the service provider (Lookout Secure Access) metadata.
-
Configure the service provider in PingOne.
-
Configure the identity provider (PingOne) in Lookout.
-
Enable SSO for the Lookout management console, endpoint client, and proxy authentication.
-
Configure IdP-initiated sign-on for Lookout management console.
-
Test SSO with Lookout Secure Access.
Step 1: Gather the SP metadata
To use PingOne as an IdP, you’ll capture SAML values from the Lookout Management console:
-
In the Lookout Management console, go to Administration → Enterprise Integration.
-
Go to Configuration → Single Sign-On.
-
On the SSO Groups tab, go to the default group.
-
In the SP Metadata column, click the Download icon.
The SP Metadata window opens.
-
Copy the Assertion Consumer Service (ACS) URL and Entity ID values.
Step 2: Configure the SP in PingOne
After you’ve captured the SAML values from Lookout Secure Access, you’ll configure a SAML-based application in PingOne. This gives PingOne the information it needs to communicate with the Lookout Cloud Security Platform so that the platform can enforce policies based on user credentials.
-
In the PingOne admin console, go to Applications → Application Catalog and browse or search for
Lookout Secure Access
. -
Click the Lookout Secure Access entry to open the details panel.
-
For Quick Setup, enter the following information:
-
ACS URL: Enter the Assertion Consumer Servicevalue that you copied previously.
-
Entity ID: Enter the Entity ID value that you copied previously.
-
-
Click Next.
-
On the Map Attributes page, click Next.
-
On the Select Groups page, click Savewithout assigning groups.
This allows users to have access to all applications by default.
Assign groups to the application to restrict access to only those groups.
-
In Application Instances, select the Lookout Secure Access Application entry to open the Connection Details page.
-
On the Connection Details page, copy the IDP Metadata URL to use when configuring the SP.
Step 3: Configure the IdP in Lookout
Next, you’ll link your PingOne instance to the Lookout Cloud Security Platform by configuring a new IdP instance. Lookout uses to retrieve user information from PingOne.
-
In the Lookout Management Console, go to Administration → Enterprise Integration.
-
Go to Configuration → Single Sign-On.
-
On the SSO Providers tab, click New.
-
Enter or select the following values:
-
Name: Enter a name that contains no more than 255 characters.
-
Type: Select Identity Provider.
-
SSO Group: Select Default.
-
Metadata Link: Enter the IDP Metadata URL value that you copied from the PingOne.
-
-
Click Validate and confirm that the Management Console populates the Entity ID field.
-
Click Save.
Step 4: Enable SSO for the Lookout management console, endpoint client, and proxy authentication
After you’ve configured the service provider, you’ll enable SSO for the Lookout Cloud Security Platform.
-
In the Lookout Management Console, go to Administration → System Settings → Enterprise Authentication.
-
In the Identity Provider list, choose the IdP that you created.
-
To enable the Management SSO, click the toggle.
-
To enable the Endpoint, click the toggle.
The Native Proxy Authentication toggle is enabled by default and cannot be disabled.
-
Click Save.
Step 5: Configure IdP-initiated sign-on for Lookout management console
Next, to set up IdP-initiated sign-on for the Lookout Management Console, you’ll configure relay state on PingOne.
-
In the Lookout Management Console, go to Administration → System Settings → Enterprise Authentication.
-
In the Enterprise Single Sign-on Settings field, click Copy to copy the Relay State value.
-
In the PingOne admin console, go to Applications → Applications.
-
Click the Lookout Secure Access entry.
-
On the Overview tab, click Enable Advanced Configuration.
The Enable Advanced Configuration window opens.
-
Click Enable.
-
On the Configuration tab, click on the Pencil icon to edit the Connection Details.
-
In the Target Application URL field, paste the Relay State value that you copied from the Lookout Management Console.
-
Click Save.
Step 6: Test SSO with Lookout Secure Access.
After you’ve configured IdP-initiated sign-on, you’ll verify that SSO works.
-
In the PingOne admin console, go to Applications → Applications.
-
Click the Lookout Secure Access entry.
-
On the Configuration tab, copy the Initiate Single Sign-On URL value.
-
Paste the URL in a new browser window and hit enter.
You are successfully redirected to the Lookout Management Console.