NotEnoughAuth 是一个适用于 Paper (1.21.7+) 的插件,它允许你基于 Dialog 功能,使用 OAuth2 提供商(Google、GitHub、GitLab、Discord、Twitch、Telegram)来验证玩家身份。
设置方法 —— 请向下滚动至 ? 配置 部分。
? 截图
* 在验证过程中,你将看到“正在加入世界...”界面。
* 验证成功后,在显示“正在加入世界...”界面后,你将自动被重定向到服务器。
? 工作原理?
每个玩家会话都有一个描述客户端状态的哈希值,每次玩家加入时都会与数据库(data.yml)进行比对。
如果会话匹配——则允许进入服务器。如果不匹配,则强制进行身份验证。
会话哈希由多个因素组成:
? 命令
/link — 打开对话框,将额外的 OAuth2 提供商链接到你的账户。
/unlink — 打开对话框,从你的账户中取消链接 OAuth2 提供商。
/logout — 终止当前的会话哈希,下次加入时需要重新验证。
/auth info — 查看可用命令列表。
/auth reload — 重载插件。
别名:/nea、/notenoughauth。
? 权限
notenoughauth.admin (默认授予 管理员) — 允许使用 /auth reload。
notenoughauth.default (默认值为 true) — 允许使用 /auth info 命令。
notenoughauth.link (默认值为 true) — 允许使用 /link 命令。
notenoughauth.unlink (默认值为 true) — 允许使用 /unlink 命令。
? 默认配置
[注意] 别忘了将你的公网 IP 填入 webIp 字段。
此外,你需要在机器上开放 TCP 端口以便插件正常工作。默认为端口 4177.
否则,一切都将无法工作。
# 设置 'webIp' 和 'webPort' 后,请查看控制台输出;
# 你会看到 OAuth2 重定向 URL 列表 - 复制这些 URL 并将其粘贴到你创建应用凭证时的 OAuth 提供商设置中(例如 Google、GitHub)。
webIp: "127.0.0.1"
webPort: 4177
# 定义认证重定向链接是否包含 "http" 或 "https";
# 例如,如果你使用 Nginx/Apache 作为反向代理 ('80' → '4177') 并使用 Cloudflare 进行 SSL 证书加密,请将此设置为 'true';
# 对于本地测试,你可以将其保留为 'false'。
useHttps: false
# 如果你使用隧道软件(如 'playit.gg' 或 'ngrok'),你可以使用此字段覆盖基础 URL(例如 'https://4be8-112-41-125-11.ngrok-free.app')。
overriddenRedirectUrlBase: ""
# 玩家完成验证过程的时间(以秒为单位)。
timeout: 90
# 创建 Google 应用的链接:
google:
enabled: true
clientId: "YOUR_GOOGLE_CLIENT_ID"
secret: "YOUR_GOOGLE_CLIENT_SECRET"
# 创建 GitHub 应用的链接: https://github.com/settings/developers
github:
enabled: true
clientId: "YOUR_GITHUB_CLIENT_ID"
secret: "YOUR_GITHUB_CLIENT_SECRET"
# 创建 GitLab 应用的链接: https://gitlab.com/-/user_settings/applications
gitlab:
enabled: true
clientId: "YOUR_GITLAB_APPLICATION_ID"
secret: "YOUR_GITLAB_SECRET"
# 创建 Discord 应用的链接: https://discord.com/developers/applications
discord:
enabled: true
clientId: "YOUR_DISCORD_CLIENT_ID"
secret: "YOUR_DISCORD_CLIENT_SECRET"
# 创建 Twitch 应用的链接: https://dev.twitch.tv/console/apps/create
twitch:
enabled: true
clientId: "YOUR_TWITCH_CLIENT_ID"
secret: "YOUR_TWITCH_CLIENT_SECRET"
# Telegram 文档链接: https://core.telegram.org/bots/telegram-login#tldr
telegram:
enabled: true
clientId: "YOUR_TELEGRAM_BOT_CLIENT_ID"
secret: "YOUR_TELEGRAM_BOT_CLIENT_SECRET"
messages:
"prefix": "&#C8D1DE[NotEnoughAuth]"
"auth-required": "&f需要身份验证才能加入此服务器。"
"title": "&#FFDB60欢迎!"
"description": "让我们使用 OAuth2 验证您的身份。\n系统将提示您打开浏览器。"
"google": "&#D5DEEAGoogle 账号"
"google-hover": "点击以进行 Google 身份验证"
"github": "&#D5DEEAGitHub 账号"
"github-hover": "点击以进行 GitHub 身份验证"
"gitlab": "&#D5DEEAGitLab 账号"
"gitlab-hover": "点击以进行 GitLab 身份验证"
"discord": "&#D5DEEADiscord 账号"
"discord-hover": "点击以进行 Discord 身份验证"
"twitch": "&#D5DEEATwitch 账号"
"twitch-hover": "点击以进行 Twitch 身份验证"
"telegram": "&#D5DEEATelegram 账号"
"telegram-hover": "点击以进行 Telegram 身份验证"
"auth-success": "身份验证成功。"
"auth-success-description": "您现在可以返回 Minecraft。"
"auth-failed": "身份验证失败。"
"account-mismatch": "此 Minecraft 账号与此 OAuth 提供商下的另一个账号关联。"
"provider-mismatch": "此提供商未与该玩家的账号关联。"
"invalid-state": "无效或过期的状态。请重试。"
"timeout": "超时。"
"link-title": "&#FFDB60关联一个提供商"
"link-description": "您可以&#A4D400&n关联&r额外的 oAuth2 提供商到您的账号,以便在此服务器上将其用作额外的登录选项。"
"link-hover": "点击以关联此提供商"
"unlink-title": "&#FFDB60取消关联一个提供商"
"unlink-description": "您可以选择一个账号&#EB4C42&n取消关联&r。如果需要,您将能够再次关联该提供商。"
"unlink-hover": "点击以取消关联此提供商"
"unlink-confirm-title": "&#FFDB60确定吗?"
"unlink-confirm-description": "此提供商将从您的账号中移除。"
"confirm-unlink": "&#E74C3C确认取消关联"
"confirm-unlink-hover": "永久取消关联此提供商"
"confirm": "&#A4D400确认"
"cancel": "&#EB4C42取消"
"back": "&#EB4C42← 返回"
"back-hover": "返回服务器列表"
"info-header": "<prefix> &#ECF4FB命令:"
"info-link": "\n &#D8E5EC&n/link&r&#ECF4FB - 将额外的提供商关联到您的账号。"
"info-unlink": "\n &#D8E5EC&n/unlink&r&#ECF4FB - 从您的账号中取消关联其中一个提供商。"
"info-logout": "\n &#D8E5EC&n/logout&r&#ECF4FB - 退出账号。"
"info-reload": "\n &#D8E5EC&n/auth reload&r&#ECF4FB - 重新加载插件配置。"
"successfully-linked": "<prefix> &#A4D400关联成功!"
"successfully-unlinked": "<prefix> &#A4D400取消关联成功!"
"provider-linked": "提供商关联成功!"
"logged-out": "&f您已成功注销。"
"reloaded": "<prefix> &#ECF4FB已重新加载!"
"disconnected": "已断开连接。"
"command-not-found": "<prefix> &#E03E3E哎呀!该命令不存在,或者您没有足够的权限。"
"not-enough-permissions": "<prefix> &#E03E3E权限不足。"
"one-provider-left": "<prefix> &#E03E3E您的账号仅剩一个关联的提供商。"
"all-providers-already-linked": "<prefix> &#ECF4FB您已将所有可能的提供商都关联到了您的账号!"
"rejoin": "<prefix> &#E03E3E会话哈希不匹配。请重新加入。"
"an-error-occurred": "<prefix> &#E03E3E重新加载期间发生错误!请检查控制台日志以获取详细信息。"
? 安装
[重要] 在开始之前,请确保插件版本与您的服务器版本兼容。
- 从 Releases 选项卡下载最新版本的插件。
- 将下载的
.jar 文件放入服务器的 /plugins 文件夹中。
- 重启服务器或输入
/reload 命令。
? 配置
[注意] 切勿分享 config.yml 中显示的客户端密钥、机器人令牌或其他凭据。任何拥有这些访问权限的人都可以冒充您的应用程序。
指南中截图中显示的所有凭据均已撤销且不再有效。
先决条件:
- 确保将服务器的公网 IP 填入
config.yml 中的 webIp 字段。
- 在服务器上打开一个 TCP 端口(默认为 4177),其值需与
config.yml 中的 webPort 字段一致。
如何配置特定提供商:
Google
-
点击链接以打开 Google Cloud Console:
-
创建一个项目:

-
点击 "Create credentials" → "OAuth client ID":

-
将 "Application type" 设置为 "Web application" 并提供名称:

-
输入 /auth reload 并复制 Google 回调链接(在此之前,请确保在配置中用服务器的公网 IP 或域名填充 webIp):

-
将来自控制台的链接添加到 "Authorized redirect URIs" 部分并点击 "Create":

-
复制 "Client ID" 和 "Client Secret":

-
在 google 部分,将 YOUR_GOOGLE_CLIENT_ID 和 YOUR_GOOGLE_CLIENT_SECRET 替换为获得的凭据:

-
✅ 输入 /auth reload 并享受吧!
GitHub
-
点击链接打开 GitHub Developer Settings:
-
点击 "New OAuth App":

-
输入 /auth reload 并复制用于 GitHub 回调的链接(在此之前,请确保在配置中填写 webIp 为你的服务器公网 IP 或域名):

-
填写 "Application name"、"Homepage URL",并将插件控制台中的重定向 URL 粘贴到 "Authorization callback URL" 字段中,然后点击 "Register application":

-
复制 "Client ID",然后单击 "Generate a new client secret" 并复制生成的密钥:

-
在 github 部分中,将 YOUR_GITHUB_CLIENT_ID 和 YOUR_GITHUB_CLIENT_SECRET 替换为获取到的凭据:

-
✅ 输入 /auth reload 并享受吧!
GitLab
-
点击链接打开 GitLab User Application Settings:
-
点击 "Add new application":

-
输入 /auth reload 并复制用于 GitLab 回调的链接(在此之前,请确保在配置中填写 webIp 为你的服务器公网 IP 或域名):

-
填写 "Name" 字段,将插件控制台中的重定向 URL 粘贴到 "Redirect URI" 字段中,并选择 read_user 作用域,然后点击 "Save application":

-
复制 "Application ID" 和 "Secret":

-
在 gitlab 部分中,将 YOUR_GITLAB_APPLICATION_ID 和 YOUR_GITLAB_SECRET 替换为获取到的凭据:

-
✅ 输入 /auth reload 并享受吧!
Discord
-
点击链接打开 Discord Developer Portal:
-
点击 "New Application",输入你的应用名称,然后点击 "Create":

-
在左侧边栏中选择 "OAuth2" 选项卡。复制 "Client ID" 和 "Client Secret":

-
输入 /auth reload 并复制用于 Discord 回调的链接(在此之前,请确保在配置中填写 webIp 为你的服务器公网 IP 或域名):

-
在同一 OAuth2 页面的 "Redirects" 部分下,点击 "Add Redirect",粘贴来自插件控制台的 redirect URL,然后点击 "Save Changes":

-
在 discord 部分中,将 YOUR_DISCORD_CLIENT_ID 和 YOUR_DISCORD_CLIENT_SECRET 替换为获取到的凭据:

-
✅ 输入 /auth reload 并享受吧!
Twitch
-
点击链接打开 Twitch Developer Console:
-
输入 /auth reload 并复制用于 Twitch 回调的链接(在此之前,请确保在配置中填写 webIp 为你的服务器公网 IP 或域名):

-
填写 "Name" 字段,将插件控制台中的重定向 URL 粘贴到 "OAuth Redirect URLs" 字段中,然后点击 "Add",接着选择任意 "Category"(例如 "Website Integration"),最后点击 "Create":

-
返回到 "Applications" 列表,找到你刚刚创建的应用,然后点击 "Manage":

-
复制 "Client ID",然后单击 "New Secret" 并复制生成的 "Client Secret":

-
在 twitch 部分中,将 YOUR_TWITCH_CLIENT_ID 和 YOUR_TWITCH_CLIENT_SECRET 替换为获取到的凭据:

-
✅ 输入 /auth reload 并享受吧!
Telegram
-
打开 Telegram 并与 @BotFather 开始聊天:
-
打开 @BotFather 迷你应用,点击 "Create a New Bot" 并按照表单操作:

-
创建机器人后,转到 "Login Widget" 选项卡:

-
点击 "Switch to OpenID Connect Login":

-
复制 "Client ID" 和 "Client Secret":

-
输入 /auth reload 并复制 Telegram 回调的基础域名/IP(在此之前,请确保在配置文件中用服务器的公共 IP 或域名填充 webIp):

-
在 "Redirect URIs" 部分下,点击 "Add a Redirect URI",粘贴来自插件控制台的重定向 URL:

-
在 telegram 部分中,将 YOUR_TELEGRAM_BOT_CLIENT_ID 和 YOUR_TELEGRAM_BOT_CLIENT_SECRET 替换为获取到的凭据:

-
✅ 输入 /auth reload 并享受吧!
? SSL 证书和 HTTPS
[注意] 如果您没有域名,像 ngrok 或 playit.gg 这样的隧道软件也可以提供 HTTPS URL - 为此请使用 config.yml 中的 overriddenRedirectUrlBase 字段。
某些 OAuth2 提供商要求您拥有域名,在某些情况下还需要 SSL 证书(即使用 'https')。
您可以在 Cloudflare、Spaceship 等网站上购买域名。
域名价格比较工具和聚合器 - .
OAuth2 提供商及其灵活性表:
| Provider |
Can use without a private domain |
Can use without SSL (HTTPS) |
Google |
❌ |
✅ |
GitHub |
✅ |
✅ |
GitLab |
✅ |
✅ |
Discord |
✅ |
✅ |
Twitch |
❌ |
❌ |
Telegram |
✅ |
✅ |
NotEnoughAuth is a Paper (1.21.7+) plugin that allows you to authenticate players using OAuth2 providers (Google, GitHub, GitLab, Discord, Twitch, Telegram) based on the Dialog functionality.
How to set up — scroll down to the ? Configuration section.
? Screenshots
* While you authenticate, you will see the 'Joining world...' screen.
* After successfully authenticating, you will be automatically redirected to the server after the 'Joining world...' screen.
? How it works?
Each player session has a hash describing the state of the client, and it is checked against the database (data.yml) each time a player joins.
If sessions match - proceed to the server. If they don't, force the authentication.
The session hash is composed of multiple factors:
? Commands
/link — opens a dialog to link an additional OAuth2 provider to your account.
/unlink — opens a dialog to unlink an OAuth2 provider from your account.
/logout — terminates your current session hash, requires authentication on next join.
/auth info — see a list of available commands.
/auth reload — reloads the plugin.
Aliases: /nea, /notenoughauth.
? Permissions
notenoughauth.admin (for operators by default) — Allows to use /auth reload.
notenoughauth.default (true by default) — Allows to use the /auth info command.
notenoughauth.link (true by default) — Allows to use the /link command.
notenoughauth.unlink (true by default) — Allows to use the /unlink command.
? Default config
[CAUTION] Don't forget to put your public IP into the webIp field.
Also, you should open the TCP port on your machine for the plugin to work. Port 4177 by default.
Otherwise, nothing will work.
# After setting 'webIp' and 'webPort', take a look at the console output;
# You will see a list of OAuth2 redirect URLs - copy these and paste them into your OAuth provider settings (e.g., Google, GitHub) when creating the application credentials.
webIp: "127.0.0.1"
webPort: 4177
# Defines whether auth redirect links will contain "http" or "https";
# For example, if you use Nginx/Apache as a reverse proxy ('80' → '4177') and Cloudflare for SSL certificate, set this to 'true';
# For local testing, you may leave this as 'false'.
useHttps: false
# If you use tunneling software (such as 'playit.gg' or 'ngrok'), you may use this field for overriding the base URL (e.g., 'https://4be8-112-41-125-11.ngrok-free.app').
overriddenRedirectUrlBase: ""
# Time for a player to pass the auth process (in seconds).
timeout: 90
# Link for creating Google application:
google:
enabled: true
clientId: "YOUR_GOOGLE_CLIENT_ID"
secret: "YOUR_GOOGLE_CLIENT_SECRET"
# Link for creating GitHub application: https://github.com/settings/developers
github:
enabled: true
clientId: "YOUR_GITHUB_CLIENT_ID"
secret: "YOUR_GITHUB_CLIENT_SECRET"
# Link for creating GitLab application: https://gitlab.com/-/user_settings/applications
gitlab:
enabled: true
clientId: "YOUR_GITLAB_APPLICATION_ID"
secret: "YOUR_GITLAB_SECRET"
# Link for creating Discord application: https://discord.com/developers/applications
discord:
enabled: true
clientId: "YOUR_DISCORD_CLIENT_ID"
secret: "YOUR_DISCORD_CLIENT_SECRET"
# Link for creating Twitch application: https://dev.twitch.tv/console/apps/create
twitch:
enabled: true
clientId: "YOUR_TWITCH_CLIENT_ID"
secret: "YOUR_TWITCH_CLIENT_SECRET"
# Link to Telegram documentation: https://core.telegram.org/bots/telegram-login#tldr
telegram:
enabled: true
clientId: "YOUR_TELEGRAM_BOT_CLIENT_ID"
secret: "YOUR_TELEGRAM_BOT_CLIENT_SECRET"
messages:
"prefix": "&#C8D1DE[NotEnoughAuth]"
"auth-required": "&fAuthentication required to join this server."
"title": "&#FFDB60Welcome!"
"description": "Let's verify it's you using OAuth2.\nYou will be prompted to open your browser."
"google": "&#D5DEEAGoogle Account"
"google-hover": "Click for Google authentication"
"github": "&#D5DEEAGitHub Account"
"github-hover": "Click for GitHub authentication"
"gitlab": "&#D5DEEAGitLab Account"
"gitlab-hover": "Click for GitLab authentication"
"discord": "&#D5DEEADiscord Account"
"discord-hover": "Click for Discord authentication"
"twitch": "&#D5DEEATwitch Account"
"twitch-hover": "Click for Twitch authentication"
"telegram": "&#D5DEEATelegram Account"
"telegram-hover": "Click for Telegram authentication"
"auth-success": "Authentication successful."
"auth-success-description": "You can now return to Minecraft."
"auth-failed": "Authentication failed."
"account-mismatch": "This Minecraft account is linked to a different account in this OAuth provider."
"provider-mismatch": "This provider isn't linked to this player's account."
"invalid-state": "Invalid or expired state. Please try again."
"timeout": "Timeout."
"link-title": "&#FFDB60Link a provider"
"link-description": "You may &#A4D400&nlink&r an additional oAuth2 provider to your account to be able to use it as your additional sign-in option on this server."
"link-hover": "Click to link this provider"
"unlink-title": "&#FFDB60Unlink a provider"
"unlink-description": "You may choose an account to &#EB4C42&nunlink&r. If needed, you will be able to link the provider again."
"unlink-hover": "Click to unlink this provider"
"unlink-confirm-title": "&#FFDB60Are you sure?"
"unlink-confirm-description": "This provider will be removed from your account."
"confirm-unlink": "&#E74C3CConfirm Unlink"
"confirm-unlink-hover": "Permanently unlink this provider"
"confirm": "&#A4D400Confirm"
"cancel": "&#EB4C42Cancel"
"back": "&#EB4C42← Back"
"back-hover": "Go back to server list"
"info-header": "<prefix> &#ECF4FBCommands:"
"info-link": "\n &#D8E5EC&n/link&r&#ECF4FB - link an additional provider to your account."
"info-unlink": "\n &#D8E5EC&n/unlink&r&#ECF4FB - unlink one of the providers from your account."
"info-logout": "\n &#D8E5EC&n/logout&r&#ECF4FB - sign out of the account."
"info-reload": "\n &#D8E5EC&n/auth reload&r&#ECF4FB - reload the plugin configuration."
"successfully-linked": "<prefix> &#A4D400Linked successfully!"
"successfully-unlinked": "<prefix> &#A4D400Unlinked successfully!"
"provider-linked": "Provider linked successfully!"
"logged-out": "&fYou've successfully logged out."
"reloaded": "<prefix> &#ECF4FBReloaded!"
"disconnected": "Disconnected."
"command-not-found": "<prefix> &#E03E3EOops! That command doesn't exist, or you don't have enough permissions."
"not-enough-permissions": "<prefix> &#E03E3ENot enough permissions."
"one-provider-left": "<prefix> &#E03E3EYou have only one provider left linked to your account."
"all-providers-already-linked": "<prefix> &#ECF4FBYou've already linked all possible providers to your account!"
"rejoin": "<prefix> &#E03E3ESession hashes don't match. Please rejoin."
"an-error-occurred": "<prefix> &#E03E3EAn error occurred during reload! Check the console logs for details."
? Installation
[IMPORTANT] Before getting started, make sure that the plugin's version is compatible with your server version.
- Download the latest version of the plugin from the Releases tab.
- Put the downloaded
.jar into the /plugins folder of your server.
- Restart your server or enter the
/reload command.
? Configuration
[CAUTION] Never share your client secrets, bot tokens, or any other credentials shown in your config.yml. Anyone with access to these can impersonate your application.
All credentials visible in the screenshots throughout the guide have been revoked and are no longer valid.
Prerequisites:
- Make sure to put your server's public IP into the
webIp field in config.yml.
- Open a TCP port (4177 by default) on your server equal to the
webPort field from the config.yml.
How to configure specific providers:
Google
-
Follow the link to open Google Cloud Console:
-
Create a project:

-
Click "Create credentials" → "OAuth client ID":

-
Set "Application type" to "Web application" and provide it with a name:

-
Enter /auth reload and copy the link for Google callback (before that, make sure to populate webIp in the configuration with your server public IP or domain):

-
Add the link from the console to the "Authorized redirect URIs" section and click "Create":

-
Copy both "Client ID" and "Client Secret":

-
In the google section, replace YOUR_GOOGLE_CLIENT_ID and YOUR_GOOGLE_CLIENT_SECRET with the obtained credentials:

-
✅ Enter the /auth reload and enjoy!
GitHub
-
Follow the link to open GitHub Developer Settings:
-
Click "New OAuth App":

-
Enter /auth reload and copy the link for GitHub callback (before that, make sure to populate webIp in the configuration with your server public IP or domain):

-
Fill in "Application name", "Homepage URL", and paste the redirect URL from the plugin console into the "Authorization callback URL" field, then click "Register application":

-
Copy the "Client ID", then click "Generate a new client secret" and copy the generated secret:

-
In the github section, replace YOUR_GITHUB_CLIENT_ID and YOUR_GITHUB_CLIENT_SECRET with the obtained credentials:

-
✅ Enter /auth reload and enjoy!
GitLab
-
Follow the link to open GitLab User Application Settings:
-
Click "Add new application":

-
Enter /auth reload and copy the link for GitLab callback (before that, make sure to populate webIp in the configuration with your server public IP or domain):

-
Fill in the "Name" field, paste the redirect URL from the plugin console into the "Redirect URI" field, and select the read_user scope, then click "Save application":

-
Copy both the "Application ID" and the "Secret":

-
In the gitlab section, replace YOUR_GITLAB_APPLICATION_ID and YOUR_GITLAB_SECRET with the obtained credentials:

-
✅ Enter /auth reload and enjoy!
Discord
-
Follow the link to open the Discord Developer Portal:
-
Click "New Application", enter a name for your application, and click "Create":

-
In the left sidebar, select the "OAuth2" tab. Copy the "Client ID" and "Client Secret":

-
Enter /auth reload and copy the link for Discord callback (before that, make sure to populate webIp in the configuration with your server public IP or domain):

-
Under the "Redirects" section on the same OAuth2 page, click "Add Redirect", paste the redirect URL from the plugin console, and click "Save Changes":

-
In the discord section, replace YOUR_DISCORD_CLIENT_ID and YOUR_DISCORD_CLIENT_SECRET with the obtained credentials:

-
✅ Enter /auth reload and enjoy!
Twitch
-
Follow the link to open the Twitch Developer Console:
-
Enter /auth reload and copy the link for Twitch callback (before that, make sure to populate webIp in the configuration with your server public IP or domain):

-
Fill in the "Name" field, paste the redirect URL from the plugin console into the "OAuth Redirect URLs" field and click "Add", then choose any "Category" (e.g. "Website Integration"), and click "Create":

-
Back on the "Applications" list, find your newly created app and click "Manage":

-
Copy the "Client ID", then click "New Secret" and copy the generated "Client Secret":

-
In the twitch section, replace YOUR_TWITCH_CLIENT_ID and YOUR_TWITCH_CLIENT_SECRET with the obtained credentials:

-
✅ Enter /auth reload and enjoy!
Telegram
-
Open Telegram and start a chat with @BotFather:
-
Open the @BotFather Mini App, click "Create a New Bot" and proceed with the form:

-
Once the bot is created, go to the "Login Widget" tab:

-
Click on the "Switch to OpenID Connect Login":

-
Copy the "Client ID" and the "Client Secret":

-
Enter /auth reload and copy the base domain/IP for the Telegram callback (before that, make sure to populate webIp in the configuration with your server public IP or domain):

-
Under the "Redirect URIs" section, click "Add a Redirect URI", paste the redirect URL from the plugin console:

-
In the telegram section, replace YOUR_TELEGRAM_BOT_CLIENT_ID and YOUR_TELEGRAM_BOT_CLIENT_SECRET with the obtained credentials:

-
✅ Enter /auth reload and enjoy!
? SSL certificates and HTTPS
[NOTE] If you don't own a domain, tunneling software like ngrok or playit.gg can also provide an HTTPS URL - use the overriddenRedirectUrlBase field in config.yml for that.
Some OAuth2 providers require you to own a domain, and in some cases, an SSL certificate (i.e., to use 'https').
You can purchase a domain at websites such as Cloudflare, Spaceship.
Domain price comparison tool and aggregator - .
Table of OAuth2 providers and their agility:
| Provider |
Can use without a private domain |
Can use without SSL (HTTPS) |
Google |
❌ |
✅ |
GitHub |
✅ |
✅ |
GitLab |
✅ |
✅ |
Discord |
✅ |
✅ |
Twitch |
❌ |
❌ |
Telegram |
✅ |
✅ |
评论 0
登录后参与评分
还没有评论,来抢沙发吧