> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/chinese/guan-li-yu-she-zhi/settings/global-settings/integration/identity-service-provider-configuration.md).

# 身份服务提供商配置

配置身份服务提供商（IdP）以与 DocBits 集成，需要执行几个特定步骤。以下是操作指南：

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-0f0717fe68866ea83f51802d1f69b7326f5a0439%2Fimage%20(199).png?alt=media" alt=""><figcaption></figcaption></figure>

**访问 IdP 配置界面**

* 以管理员身份登录身份服务提供商（IdP）。
* 前往用于管理 SAML 集成的设置或配置界面。

**输入租户 ID：**

* 找到可配置新 SAML 集成的部分。
* 输入 DocBits 租户 ID。此 ID 用于向 IdP 标识您的 DocBits 账户，并支持两个系统之间的安全通信。

**导入所需文件：**

* DocBits 通常要求下载元数据或添加特定配置详细信息。请查阅 IdP 文档，了解所需步骤。
* 下载 DocBits 元数据文件，或将其导入 IdP 的配置菜单。您也可以根据 IdP 支持的功能，手动输入所需的配置详细信息。

**配置集成设置：**

* 确保集成设置（例如 SSO URL、实体 ID 和 SAML 证书）正确无误。
* 检查单点注销（SLO）URL 和其他必需参数是否配置正确。这些参数对于通过 SAML 顺利进行身份验证和注销至关重要。

**验证配置：**

* 仔细检查所有输入的信息是否正确，以及是否存在拼写错误或配置错误。
* 运行测试，确保用户能够通过 SAML 成功登录 DocBits，并且单点注销功能正常运行。

**安全注意事项：**

* 确保安全处理所有传输的文件和配置详细信息，以避免数据泄露或未经授权的访问。
* 防止未经授权的人员访问 SAML 证书和凭据等敏感信息，并将其存放在安全的位置。


---

# 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.docbits.com/chinese/guan-li-yu-she-zhi/settings/global-settings/integration/identity-service-provider-configuration.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.
