> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/run-the-platform/zh/shen-fen-yan-zheng/oidc-apps-overview.md).

# VergeOS OIDC 应用概览

VergeOS OpenID Connect（OIDC）功能概览，用于集中式身份管理、跨 VergeOS 系统和租户的单点登录以及上游身份提供商集成。

VergeOS 提供 OIDC 功能，支持多个 VergeOS 系统和/或租户的集中式身份管理。

## VergeOS OIDC 应用的优势

* 能够将 VergeOS 系统建立为身份提供方（可配合或不配合上游提供方，如 Google、Azure 等）
* 上游授权提供方中的同一应用/令牌可用于多个物理环境和租户，而无需为每个环境单独创建。
* 在各个 VergeOS 系统之间提供单点登录（SSO）功能
* MSP/提供商可拥有与其环境关联的集中登录，用于所有租户
* OIDC 提供了一种标准化、广泛支持且内置安全功能的协议
* 在跨 VergeOS 系统/租户进行用户/组管理时，行政负担更轻

## 一般操作流程

* 用户尝试登录到 VergeOS 系统
* 请求会被重定向到 VergeOS 身份提供方系统
* 当配置了第三方提供方时，请求会根据需要重定向到上游（例如 Google 身份验证）
* 包含用户信息的令牌会返回到最初的 VergeOS 系统
* 令牌被验证后，创建用户会话

## 配置步骤

配置中央 VergeOS 身份提供方涉及以下步骤：

1. 在将作为 VergeOS 身份提供方的系统上创建任何上游授权来源（如 Google、Azure、Okta）。
2. [将 VergeOS 设置为 OIDC 提供方](/knowledge-base/zh/system-administration/setting-up-vergeos-as-identity-provider-oidc.md)

{% hint style="success" %}
**同一系统上可创建多个 OIDC 应用，以适应不同配置。**
{% endhint %}

3. [将 VergeOS 配置为 OIDC 客户端](/knowledge-base/zh/system-administration/configuring-vergeos-as-oidc-client.md)

有关详细的实施指导和故障排除，请参阅上方链接的知识库文章。


---

# 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.verge.io/run-the-platform/zh/shen-fen-yan-zheng/oidc-apps-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.