WP Manifestindependent plugin directory
manifest / integrations / wpos-oauth-bridge

WPOS OAuth 代理

将站点发出的 Google 和 X OAuth 请求转发到 Cloudflare Worker 的 WordPress 插件。

by liutao91.cn · github.com/liutao91/wpos-oauth-bridge

0stars
0forks

Install

No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:

wp plugin install https://github.com/liutao91/wpos-oauth-bridge/archive/refs/heads/main.zip

将站点发出的 Google、X 和 GitHub OAuth 请求转发到 Cloudflare Worker 的 WordPress 插件。

功能

  • 支持 Google OAuth 请求代理
  • 支持 X OAuth 请求代理
  • 支持 GitHub OAuth 请求代理
  • 支持按站点开关单独启用或关闭
  • 支持后台配置 Worker 基础地址和访问密钥
  • 支持插件列表页快捷进入设置

安装

  1. 将整个 wpos-oauth-bridge 目录放到 WordPress 的 wp-content/plugins/ 目录下。
  2. 在后台启用插件。
  3. 进入 设置 -> WPOS OAuth 代理 配置 Worker 地址、密钥和启用的站点。

配置说明

  • Worker Base URL:Cloudflare Worker 的基础地址,例如 https://oauth.example.com/
  • API Secret:Worker 校验用的密钥
  • 代理站点:勾选需要走代理的服务,未勾选的请求不会转发

适用场景

适合需要统一中转 Google、X 或 GitHub OAuth 请求的 WordPress 站点。插件通过 WordPress 的 HTTP 请求过滤链路工作,因此只要目标登录插件走的是同一套请求流程,就可以被适配。

English

WPOS OAuth Bridge

A WordPress plugin that forwards Google, X, and GitHub OAuth requests from your site to a Cloudflare Worker.

Features

  • Proxies Google OAuth requests
  • Proxies X OAuth requests
  • Proxies GitHub OAuth requests
  • Enables or disables each provider independently
  • Stores Worker base URL and API secret in the admin settings
  • Adds a quick Settings link on the Plugins page

Installation

  1. Copy the wpos-oauth-bridge folder into wp-content/plugins/.
  2. Activate the plugin in WordPress.
  3. Go to Settings -> WPOS OAuth 代理 and configure the Worker URL, secret, and enabled providers.

Configuration

  • Worker Base URL: the base URL of your Cloudflare Worker, for example https://oauth.example.com/
  • API Secret: the shared secret used to validate requests
  • Proxy Providers: enable only the services you want to proxy

Use Case

This plugin is designed for WordPress sites that need to centralize Google, X, or GitHub OAuth traffic through a Worker. It works through WordPress' HTTP request filter, so any login plugin using the same request path can benefit from the proxy layer.