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

# Single Sign On

TrustLogix supports Single Sign-On (SSO) integration with multiple Identity Providers (IdPs) to enhance security and simplify authentication for enterprise users. The integration allows users to log in to TrustLogix using their organization's authentication system, ensuring seamless and secure access management.

***

### **Supported Identity Providers (IdPs)**

TrustLogix supports integration with the following IdPs:

* **Azure AD**
* **Okta**
* Other IdPs supporting **SAML 2.0** authentication

Each IdP has a similar integration process, which involves configuring SAML-based authentication, exchanging metadata, and setting up user provisioning where applicable.

***

### **General Steps for SSO Integration**

#### **1. Configure Enterprise Application in IdP**

* Log in to the IdP's admin console.
* Create a new **Enterprise Application** for TrustLogix.
* Select **SAML-based authentication**.
* Provide required TrustLogix SAML attributes, such as:
  * **ACS (Assertion Consumer Service) URL**: `https://trustlogixhostname/api/federation/{tenant_id}/sso`
  * **Entity ID**: `https://trustlogixhostname/api/federation/{tenant_id}/metadata`
* Download the **Federation Metadata XML** from the IdP.

> Replace trustlogixhostname with hostname shared for front end use.

#### **2. Configure SSO in TrustLogix**

* Log in to TrustLogix with **Super Admin** privileges.
* Navigate to **Integrations → SSO**.
* Create an SSO integration by providing:
  * **Integration Name** (e.g., "Azure AD SSO")
  * **Metadata XML** downloaded from IdP
  * **Redirect URL** (User Access URL from IdP)
* Save and enable the integration.


---

# 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.trustlogix.io/integrations/single-sign-on.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.