> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-client-integration-guide/ras-web-client-api/authentication-handoff-api/example.md).

# Example

The example below launches published resource `2` for a user from a browser page on your portal. The payload is submitted as a standard form-style POST so that the browser follows the Gateway's 302 redirect as a top-level navigation.

```html
<script>
function launchResource(username, password) {
  const payload = {
    username: username,
    password: password,
    login: "https://your-portal.example.com/login",
    logout: "https://your-portal.example.com/logout",
    appid: 2,
    theme: "dark",
    extra: {
      redirectLinks: true,
      redirectSound: true
    }
  };

  // Submit as a top-level POST so the browser follows the 302 redirect
  const form = document.createElement("form");
  form.method = "POST";
  form.action = "https://gateway.example.com/userportal/auth-handoff";

  // <adjust field encoding to match the Gateway's expected content type>

  document.body.appendChild(form);
  form.submit();
}
</script>
```

After the POST:

1. The Gateway validates the credentials.
2. The Gateway responds with a `302` and a **Location** header pointing to the User Portal destination.
3. The browser navigates to the User Portal, where the user is signed in, and resource `2` is launched.

To sign the user in to the User Portal without launching a specific resource, omit **appid** — the user will see all published resources available to them.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parallels.com/landing/ras-client-integration-guide/ras-web-client-api/authentication-handoff-api/example.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.