> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/disaster-recovery-and-live-backup/configure-the-live-backup-environment/configure-live-backup-for-multiple-samls.md).

# Configure Live Backup for Multiple SAMLs

Configure Cortex XSOAR 6.14 live backup for environments that use multiple SAML identity providers.

These steps describe how to configure live backup for multiple SAMLs by configuring SAML integrations for each server.

1. Verify the **External Host Name** value matches the URL of the production server by going to Settings → ABOUT → Troubleshooting → **Server Configuration**.
2. On the production server:
   1. Go to Settings → INTEGRATIONS → **Instances** and search for **SAML 2.0**.
   2. Create a SAML integration by clicking **Add Instance**.
   3. Add the required parameters. For more information about setting up a SAML integration, see [Authenticate Users with SAML 2.0](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/users-and-roles/authenticate-users-with-saml-2.0.md).

      Ensure that **Service Provider Entity ID** parameter matches the URL of the production server. This is the only valid value. For example, **`https://prod.demisto.com/saml`**.
   4. Verify that you can access the production server using SSO authentication.
3. On the disaster recovery (DR) server:
   1. Create a SAML integration by repeating step 2.

      Ensure that the **Service Provider Entity ID** parameter matches the URL of the DR server. This is the only valid value. For example, **`https://dr.demisto.com/saml`**.
   2. Verify that you can access the production server.
4. (Optional) For Dev/Test environments, switch to the DR server and test the SSO login.


---

# 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://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/disaster-recovery-and-live-backup/configure-the-live-backup-environment/configure-live-backup-for-multiple-samls.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.