---
title: IdP deployment note
description: "The adapter configuration supports a \"login URL\" parameter. If the WAM session cookie is not found in the request, then the PingFederate server redirects the request to the URL page along with the relative resumePath, which is generated from PingFederate and intended for asynchronous communication between the adapter and the external application. (The state is saved in PingFederate, and processing is resumed when the application redirects to the resumePath.)"
component: webAccessManagement
page_id: webAccessManagement:web_access_management_wam_integration_kit:pf_wam_ik_idp_deployment_note
canonical_url: https://docs.pingidentity.com/integrations/webAccessManagement/web_access_management_wam_integration_kit/pf_wam_ik_idp_deployment_note.html
revdate: June 18, 2024
---

# IdP deployment note

The adapter configuration supports a "login URL" parameter. If the WAM session cookie is not found in the request, then the PingFederate server redirects the request to the URL page along with the relative `resumePath,` which is generated from PingFederate and intended for asynchronous communication between the adapter and the external application. (The state is saved in PingFederate, and processing is resumed when the application redirects to the `resumePath`.)

The login URL page can authenticate the user and redirect the request back to PingFederate. An example of a JSP code snippet for redirecting the request is shown below.

```javascript
<%
  String resumePath = request.getParameter("resumePath");
    if(resumePath != null) {
      resumePath = <PingFed_URL> + resumePath; (1)
      response.sendRedirect(resumePath);
    }
%>
```

|       |                                                                        |
| ----- | ---------------------------------------------------------------------- |
| **1** | `<PingFed_URL>` is the fully-qualified URL of the PingFederate server. |