> For the complete documentation index, see [llms.txt](https://docs.sfox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sfox.com/connect/single-sign-on/overview.md).

# Overview

SSO integrations enable partners to seamlessly authenticate users to sFOX and utilize sFOX's front end

## Introduction

sFOX Connect SSO enables you to:

1. Onboard and authenticate your users to sFOX 
2. Interact with your users' sFOX accounts (i.e. trading, custody, staking, etc.)
3. Leverage sFOX's front end application for your users as desired

sFOX Connect supports Identity Provider (IdP) initiated single sign-on (SSO)–a method of authentication that allows your users to log in to sFOX using a single set of credentials. You, the IdP, are responsible for providing the user's identity and providing the necessary authentication credentials to the sFOX application when your user wants to access it.

In an IdP-initiated SSO scenario, the user first logs in to your application (the IdP), which then sends an authentication request to the sFOX application on behalf of your user. sFOX then verifies that the authentication request originated from you and grants your user access without requiring the user to leave your application or enter their credentials again.

sFOX Connect SSO supports Security Assertion Markup Language (SAML) for exchanging authentication and authorization information between the your application (IdP) and sFOX.

## How it works

SSO integrations involve using both an iframe and server side component to access the sFOX Connect APIs.

**The sFOX Connect flow** begins when your user wants to access sFOX's products and features in your app

<figure><img src="https://953341424-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSqieKWDmfvEO9Y0sbJUb%2Fuploads%2FzlUQ9fcAsKGUBmO0Kp9l%2FsFOX%20Connect%20Flows%402x%20(1).png?alt=media&amp;token=d8e86e4f-55c6-4b32-aee1-74db575d7f5c" alt=""><figcaption></figcaption></figure>

<figure><img src="https://953341424-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSqieKWDmfvEO9Y0sbJUb%2Fuploads%2FjgG56dU8ZFxkrWsHUzUd%2FGroup%201003.png?alt=media&amp;token=3df43354-d3fe-4deb-b3bb-3d77b051d001" alt=""><figcaption><p>Example SSO Authentication Screen</p></figcaption></figure>


---

# 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.sfox.com/connect/single-sign-on/overview.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.