> 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/troubleshooting-common-issues.md).

# 常见问题排查

以下是将 DocBits 与身份服务提供商（IdP）或其他服务集成时，排查常见问题的步骤：

* **验证配置：** 确保 DocBits 中的集成设置配置正确，并符合身份服务提供商的要求。尤其要检查 SSO URL、Entity ID 和证书。
* **监控日志：** 监控 DocBits 和身份服务提供商端的日志，查找错误消息或警告。这些日志可以帮助判断问题所在。
* **验证网络连接：** 确保没有影响 DocBits 与身份服务提供商之间通信的网络问题。检查防火墙设置、DNS 配置和网络访问规则。
* **测试 SSO 流程：** 通过单点登录（SSO）执行测试登录，确保用户成功通过身份验证并重定向到 DocBits。请留意任何错误消息或重定向问题。
* **检查权限：** 确保 DocBits 中的用户拥有访问相应功能或资源所需的权限。检查组和角色的分配情况。
* **更新证书：** 确保双方的 SAML 证书和元数据均为最新版本。如果证书已过期，必须更新证书并重新测试集成。
* **联系支持：** 如果无法确定问题原因，请联系 DocBits 支持团队或您的身份服务提供商。他们可以帮助您排查问题，并针对您的设置提供具体指导。

按照这些排查步骤，您可以快速发现并解决 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/troubleshooting-common-issues.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.