> 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/configuring-single-sign-on-sso.md). # 配置单点登录（SSO）在 DocBits 中配置单点登录（SSO）需要几个步骤。以下是分步指南： **访问 SSO 设置：**

* 以管理员身份登录 DocBits 账户。 * 前往设置，找到 Single Sign-On 或 SSO。 **配置 SSO 参数：**

* 输入所需的 SSO 参数，例如实体 ID、单点注销（SLO）URL 和单点登录（SSO）URL。 * 实体 ID 是服务或应用程序的唯一标识符。 * SLO URL 是用于单点注销的 URL，可在需要时将用户从所有服务中注销。 * SSO URL 是将用户重定向到身份提供商以进行身份验证的 URL。 **下载证书和元数据：**

* 身份提供商（IdP）通常会提供证书，DocBits 使用该证书验证 SAML 身份验证响应。 * 下载证书并妥善保管。 * 元数据下载文件包含 SSO 集成所需的全部配置信息，包括实体 ID、SSO URL、证书信息等。 * 下载元数据并保存在本地，或提供给身份提供商。 **身份提供商（IdP）配置：**

* 登录身份提供商，并配置用于 SAML 集成的应用程序或服务。 * 使用已下载的元数据或手动输入的 SSO 参数，将 DocBits 添加为受信任的应用程序或服务。 * 确保 IdP 的配置与 DocBits 中指定的 SSO 参数一致。 **测试 SSO 集成：** * 配置完成后，测试 SSO 集成，确保用户可以通过 SSO 成功登录 DocBits。 * 还要验证单点注销是否正常工作：从 DocBits 注销，并确认同时也已从其他已连接的服务中注销。正确配置 SSO 后，用户即可使用现有凭据无缝登录 Docbits，从而改善用户体验并提高安全性。 --- # 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/configuring-single-sign-on-sso.md?ask=&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.