diff --git a/docs/.vitepress/config.ts b/docs/.vitepress/config.ts
index 65ee591..f0c9514 100644
--- a/docs/.vitepress/config.ts
+++ b/docs/.vitepress/config.ts
@@ -8,7 +8,7 @@ export default defineConfig({
       postChat({
         // 账户设置
         key: 'P-915FBDZX7U944XJF', // 可以到 https://ai.tianli0.top/ 获取账户KEY
-        
+
         // 文章摘要设置
         enableSummary: false, // 是否启用文章摘要
         postSelector: '#VPContent .container > .content', // 文章选择器
@@ -31,18 +31,18 @@ export default defineConfig({
           bottom: "16px", // 按钮底部位置
           left: "16px", // 按钮左侧位置
           width: "44px", // 按钮宽度
-          
+
           // 功能配置
           defaultInput: false, // 自动填充当前页面标题
           upLoadWeb: true,   // 上传网站到知识库
           showInviteLink: true, // 显示邀请链接
           addButton: true,   // 是否显示悬浮按钮
-          
+
           // 界面配置
           userTitle: "智能助手", // 用户标题
           userDesc: "如果你对部署的内容有任何疑问，可以来问我哦～", // 用户描述
           userIcon: "", // 自定义界面图标URL
-          
+
           // 预设问题配置
           defaultChatQuestions: [
             "如何部署这个项目？",
@@ -107,6 +107,7 @@ export default defineConfig({
               { text: "接入说说", link: "/exts/talks" },
               { text: "自定字段", link: "/exts/custom" },
               { text: "访客统计", link: "/exts/statistic" },
+              {text:"OAuth2/OIDC 登录",link:"/exts/oauth2"}
             ],
           },
           {
@@ -172,6 +173,7 @@ export default defineConfig({
               { text: "Qexo Talks", link: "/en/exts/talks" },
               { text: "Custom Fields", link: "/en/exts/custom" },
               { text: "PV Statistic", link: "/en/exts/statistic" },
+              {text:"OAuth2/OIDC Login",link:"/en/exts/oauth2"}
             ],
           },
           {
diff --git a/docs/en/exts/oauth2.md b/docs/en/exts/oauth2.md
new file mode 100644
index 0000000..a4a2277
--- /dev/null
+++ b/docs/en/exts/oauth2.md
@@ -0,0 +1,123 @@
+# OAuth2/OIDC Login
+
+This tutorial will help you integrate OAuth2/OIDC login functionality into Qexo in minutes.
+
+## Important Notes
+
+1. OAuth2/OIDC functionality requires Qexo >= 4.0.0 and a modern browser.
+
+2. Before using this tutorial, you need to prepare the identity provider integration information.
+
+## Adding an Identity Provider
+
+Please copy the following configuration template to your local text editor and configure it according to the specific
+provider type.
+
+```json
+
+{
+  "oidc_provider": {
+    "type": "oidc",
+    "info": {
+      "server_metadata_url": "https://example.com/.well-known/openid-configuration",
+      "client_id": "YOUR_CLIENT_ID",
+      "client_secret": "YOUR_CLIENT_SECRET",
+      "client_kwargs": {
+        "scope": "openid profile"
+      }
+    },
+    "friendly_name": "Display Name",
+    "icon": "https://example.com/icon.png"
+  },
+  "github": {
+    "type": "github",
+    "info": {
+      "client_id": "YOUR_CLIENT_ID",
+      "client_secret": "YOUR_CLIENT_SECRET",
+      "client_kwargs": {
+        "scope": ""
+      }
+    },
+    "friendly_name": "GitHub",
+    "icon": "https://example.com/github-icon.png"
+  }
+}
+```
+
+This template provides two different types of provider examples
+
+### Providers that support the OIDC specification, such as Google, Authentik
+
+1. Rename `oidc_provider` to your own provider name. This name will not be displayed on the page; it should be a short
+   English word.
+
+<h4>Note that in the configuration file, the provider name (i.e., the content at the `oidc_provider` location) must be
+unique.</h4>
+
+2. Based on your provider configuration, modify `server_metadata_url`, `client_id`, and `client_secret`.
+
+3. Modify `friendly_name` and `icon`, which will determine how the provider is displayed on the front end.
+
+4. If you don't need them, remove the unnecessary `github` field from the configuration file.
+
+5. On your provider's end, set the callback URL to
+   `https://<your Qexo address>/api/oauth/callback/<the provider name you set in step 1>`.
+
+<h4>About OpenID Scopes:</h4>
+
+Qexo only requires two scopes: openid and profile. You can add other scopes, but they won't work by default.
+
+### Providers that do not support the OIDC specification, such as GitHub
+
+<h4>For providers that do not support the OIDC specification, Qexo currently only supports GitHub. You can modify the
+code yourself if needed.</h4>
+
+1. Obtain `client_id` and `client_secret` from GitHub and fill them into the configuration file.
+
+2. Configure the icon to point to the GitHub logo. URL
+
+3. Set the callback URL for the GitHub OAuth App to `https://<your Qexo address>/api/oauth/callback/github`
+
+4. If you don't need it, remove the `oidc_provider` field from the configuration file.
+
+## Apply your configuration file
+
+In the environment variable editor, create a new environment variable named `OAUTH_PROVIDERS`, and set the entire
+configuration file as its value.
+
+### Optional: Enable SSO Only Login
+
+<h4>Note: Enabling this feature will disable Qexo's default username+password login passkey login, allowing only
+third-party logins.</h4>
+
+For security reasons, SSO Only Login has the following limitations:
+
+1. SSO Only Login will not work if no identity provider is configured.
+
+2. SSO Only Login will not work if a provider is configured but not linked to your local Qexo user in the settings.
+
+3. When SSO Only Login is enabled, users are not allowed to unbind their last third-party identity.
+
+If you are sure you want to use SSO-only login, please set the environment variable `SSO_ONLY=1`.
+
+You can safely enable this feature during initial deployment; Qexo will not disable password/passkey login if an identity is
+not bound.
+
+## Linking Your Third-Party Account
+
+1. Log in to Qexo as usual.
+
+2. Click the settings button in the upper right corner.
+
+3. Click the Manage Third-Party Account Bindings button.
+
+4. Bind your third-party identity here.
+
+This completes the configuration of Qexo's OAuth/OIDC login functionality.
+
+------
+
+### Contributions and Extensions
+
+If you need to integrate other non-standard OAuth2 providers besides GitHub, you can refer to the implementations of
+`hexoweb.libs.oauth.OAuthProvider` and its subclasses.
\ No newline at end of file
diff --git a/docs/exts/oauth2.md b/docs/exts/oauth2.md
new file mode 100644
index 0000000..d6f3e58
--- /dev/null
+++ b/docs/exts/oauth2.md
@@ -0,0 +1,96 @@
+# OAuth2/OIDC 登录
+
+这个教程将帮助你在几分钟内为 Qexo 接入 OAuth2/OIDC 登录功能
+
+## 须知
+
+1. Auth2/OIDC 功能要求 Qexo >= 4.0.0，且使用现代浏览器
+2. 在使用这个教程前，你需要准备好身份提供方的接入信息
+
+## 添加身份提供方
+
+请复制如下配置模板到您本地的文本编辑器，参照具体的提供商类型进行配置
+
+```json
+{
+  "oidc_provider": {
+    "type": "oidc",
+    "info": {
+      "server_metadata_url": "https://example.com/.well-known/openid-configuration",
+      "client_id": "YOUR_CLIENT_ID",
+      "client_secret": "YOUR_CLIENT_SECRET",
+      "client_kwargs": {
+        "scope": "openid profile"
+      }
+    },
+    "friendly_name": "Display Name",
+    "icon": "https://example.com/icon.png"
+  },
+  "github": {
+    "type": "github",
+    "info": {
+      "client_id": "YOUR_CLIENT_ID",
+      "client_secret": "YOUR_CLIENT_SECRET",
+      "client_kwargs": {
+        "scope": ""
+      }
+    },
+    "friendly_name": "GitHub",
+    "icon": "https://example.com/github-icon.png"
+  }
+}
+```
+
+该模板提供了两个不同类型的提供商示例
+
+### 支持 OIDC 规范的提供商，如Google, Authentik
+
+1. 将`oidc_provider`更名为您自己的提供商名称，这个名称不会显示在页面上，它应该是简短的英文单词
+   <h4>请注意，在配置文件中，提供商名称（即`oidc_provider`这个位置的内容）必须是唯一的</h4>
+2. 根据您的提供商配置，修改`server_metadata_url` `client_id` `client_secret`
+3. 修改`friendly_name`和`icon`，这将决定在前端如何显示提供商
+4. 如您不需要，删除配置文件中不需要的`github`字段
+5. 在您的提供商处，设置回调 URL 为 `https://<您的Qexo地址>/api/oauth/callback/<您第一步设置的提供商名称>`
+
+<h4> 关于OpenID Scopes: </h4>
+
+Qexo 只需要 openid 与 profile 两个 scopes,您可以添加其他的scope，但在默认情况下不起作用
+
+### 不支持 OIDC 规范的提供商，如 GitHub
+
+<h4> 对于不支持 OIDC 规范的提供商，Qexo 目前只支持 GitHub，如您有需要可以自行修改代码</h4>
+
+1. 从 GitHub 处获得 `client_id` `client_secret` 填入配置文件
+2. 将 icon 配置为一个指向 GitHub 微标的 URL
+3. 将 GitHub OAuth App 的回调 URL 设置为`https://<您的Qexo地址>/api/oauth/callback/github`
+4. 如您不需要，删除配置文件中的`oidc_provider`字段
+
+## 应用您的配置文件
+
+在环境变量编辑中，新建一个名为`OAUTH_PROVIDERS`的环境变量，将刚刚的配置文件全文作为环境变量的值
+
+### 可选：启用 仅SSO 登录功能
+
+<h4> 注意：开启本功能后，Qexo 默认的用户名+密码登录与通行密钥登录都会被禁用，仅允许使用第三方登录 </h4>
+
+安全起见，仅 SSO 登录功能有以下限制
+
+1. 未配置任何的身份提供商时，仅 SSO 登录功能不会生效
+2. 已配置提供商，但未在设置中将其链接到您的 Qexo 本地用户时，仅 SSO 登录功能不会生效
+3. 当仅 SSO 登录功能开启时，不允许用户解绑最后一个第三方身份
+
+如您确定使用仅 SSO 登录功能，请设置环境变量`SSO_ONLY=1`  
+您可以放心在初次部署时启用该功能，Qexo 不会在未进行身份绑定时关闭密码/密钥登录功能
+
+## 链接您的第三方账户
+
+1. 同往常一样登录 Qexo
+2. 单击右上角的设置按钮
+3. 点击 管理第三方账号绑定 按钮
+4. 在此绑定您的第三方身份
+
+至此，Qexo 的 OAuth/OIDC登录功能配置结束
+
+------
+### 贡献与扩展 
+如果你需要接入除 GitHub 以外的其他非标准 OAuth2 提供商，可以参考 `hexoweb.libs.oauth.OAuthProvider` 及其子类下的实现。
\ No newline at end of file