---
title: SP process overview
description: The following figure illustrates the request flow and how the WAM SP Adapter leverages a SAML/WS-Federation assertion to create a WAM session cookie.
component: webAccessManagement
page_id: webAccessManagement:web_access_management_wam_integration_kit:pf_wam_ik_sp_process_overview
canonical_url: https://docs.pingidentity.com/integrations/webAccessManagement/web_access_management_wam_integration_kit/pf_wam_ik_sp_process_overview.html
revdate: June 18, 2024
section_ids:
  processing-steps: Processing Steps
---

# SP process overview

The following figure illustrates the request flow and how the WAM SP Adapter leverages a SAML/WS-Federation assertion to create a WAM session cookie.

![ezn1563995791248](_images/ezn1563995791248.jpg)

## Processing Steps

1. The PingFederate SP server receives a SAML/WS-Federation assertion from the IdP.

2. PingFederate parses the assertion.

3. The WAM SP Adapter uses the WAM plug-in to create a WAM session cookie and embeds the cookie in the response.

4. A request containing the WAM session cookie is redirected to the browser.

5. The request is then redirected to the SP Application, which is protected by the third-party WAM Web Agent.

6. The third-party WAM Web Agent intercepts the request, extracts and validates the WAM session cookie, and allows access to the application.