---
title: Overview of the SSO flow
description: The following figure illustrates an example SSO process flow.
component: crowdstrike
page_id: crowdstrike::pf_crowdstrike_ik_overview_of_the_sso_flow
canonical_url: https://docs.pingidentity.com/integrations/crowdstrike/pf_crowdstrike_ik_overview_of_the_sso_flow.html
revdate: June 10, 2024
---

# Overview of the SSO flow

The following figure illustrates an example SSO process flow.

![A diagram illustrating a typical sign-on process leveraging the CrowdStrike Integration Kit.](_images/ojg1707777369202.png)

1. A user initiates the sign-on process by requesting access to a protected resource.

2. The [Google Chrome Enterprise Device Trust IdP Adapter](../google/google_chrome_enterprise_integration_kit/pf_google_chrome_enterprise_ik.html) determines if the incoming request is from the Google Chrome Enterprise browser. If so, the authentication request goes through the adapter flow, which fulfills core contract attributes, such as the **CrowdStrike Agent ID**.

3. The **CrowdStrike Agent ID** is made available to the CrowdStrike IdP Adapter.

4. The adapter invokes the configured CrowdStrike Service API for the agent ID that it received.

5. If the CrowdStrike incident returns with a score, the risk level value is fulfilled based on the threshold level scores configured in the adapter. Learn more in [CrowdStrike IdP Adapter settings reference](setup/pf_crowdstrike_ik_crowdstrike_idp_adapter_settings_reference.html).

6. The authentication policy can use the risk level value in subsequent decision making.