Sign in with Telegram Login Widget #1546

New Issue

GiteaMirror · 2026-03-13T08:46:59-05:00

GiteaMirror commented

2026-03-13 08:46:59 -05:00

Originally created by @Re4GD on GitHub (Jul 21, 2025).

https://core.telegram.org/widgets/login

Telegram login does not follow the standard oauth implementation. Custom plugin for submitting and validating the window.Telegram.Login.auth() callback is needed. I can open a PR to implement this plugin

Originally created by @Re4GD on GitHub (Jul 21, 2025). https://core.telegram.org/widgets/login Telegram login does not follow the standard oauth implementation. Custom plugin for submitting and validating the window.Telegram.Login.auth() callback is needed. I can open a PR to implement this plugin

GiteaMirror added the plugin label 2026-03-13 08:46:59 -05:00

GiteaMirror commented

2026-03-13 08:47:01 -05:00

@Kinfe123 commented on GitHub (Jul 22, 2025):

Yeah. feel free to do that.

@Kinfe123 commented on GitHub (Jul 22, 2025): Yeah. feel free to do that.

GiteaMirror commented

2026-03-13 08:47:02 -05:00

@iatomic1 commented on GitHub (Jul 26, 2025):

@Re4GD wen pr?

@iatomic1 commented on GitHub (Jul 26, 2025): @Re4GD wen pr?

GiteaMirror commented

2026-03-13 08:47:03 -05:00

@Re4GD commented on GitHub (Jul 26, 2025):

I'll open in a few days, been busy. Also trying to polish the plugin

@Re4GD commented on GitHub (Jul 26, 2025): I'll open in a few days, been busy. Also trying to polish the plugin

GiteaMirror commented

2026-03-13 08:47:04 -05:00

@iatomic1 commented on GitHub (Jul 26, 2025):

I'll open in a few days, been busy. Also trying to polish the plugin

Okay man, would ur plugin also provide linking an already existing user to their tg acct?

@iatomic1 commented on GitHub (Jul 26, 2025): > I'll open in a few days, been busy. Also trying to polish the plugin Okay man, would ur plugin also provide linking an already existing user to their tg acct?

GiteaMirror commented

2026-03-13 08:47:04 -05:00

@Re4GD commented on GitHub (Jul 26, 2025):

Didn’t think of that actually, I will add that for sure

@Re4GD commented on GitHub (Jul 26, 2025): Didn’t think of that actually, I will add that for sure

GiteaMirror commented

2026-03-13 08:47:05 -05:00

@iatomic1 commented on GitHub (Jul 26, 2025):

Is this authentication plugin designed exclusively for bots?
I'm building a Telegram bot (not a mini app) and want to add authentication to restrict access to certain commands until the user successfully authenticates

@iatomic1 commented on GitHub (Jul 26, 2025): Is this authentication plugin designed exclusively for bots? I'm building a Telegram bot (not a mini app) and want to add authentication to restrict access to certain commands until the user successfully authenticates

GiteaMirror commented

2026-03-13 08:47:06 -05:00

@Re4GD commented on GitHub (Jul 26, 2025):

The plugin is for Telegram login via Telegram Login Widget. Essentially like social Telegram login. (Just like sign in with Google, it opens a window, you sign in, it gets redirected to your page or a callback is called)

What do you mean by “authentication” and “until the user successfully authenticates”? Do you want to connect the tg bot with your web app? What is the use case here

@Re4GD commented on GitHub (Jul 26, 2025): The plugin is for Telegram login via Telegram Login Widget. Essentially like social Telegram login. (Just like sign in with Google, it opens a window, you sign in, it gets redirected to your page or a callback is called) What do you mean by “authentication” and “until the user successfully authenticates”? Do you want to connect the tg bot with your web app? What is the use case here

GiteaMirror commented

2026-03-13 08:47:07 -05:00

@iatomic1 commented on GitHub (Jul 26, 2025):

Yes wanna connect the tg bot to my web app
Currently building like a wallet tracker app, web app is done auth is in better auth of course but I want users to be able to manage their wallets through my tg bot as well
Tried using ott one time token my bot verifies it but when I get the session it returns null so I thought your plugin could fix it
Ig they are 2 diff things

@iatomic1 commented on GitHub (Jul 26, 2025): Yes wanna connect the tg bot to my web app Currently building like a wallet tracker app, web app is done auth is in better auth of course but I want users to be able to manage their wallets through my tg bot as well Tried using ott one time token my bot verifies it but when I get the session it returns null so I thought your plugin could fix it Ig they are 2 diff things

GiteaMirror commented

2026-03-13 08:47:07 -05:00

@Re4GD commented on GitHub (Jul 26, 2025):

This plugin can partially fix your problem,

The telegram user ids are unique so what you can do is:

if the user is on web, make them login with telegram, or link with telegram (this is about this plugin). then tell them that you have a tg bot as well (you can link them to the bot with a start param: t . me/mybot?start=param1, it was something like that. you can use the verification table for creating an otp. verification => telegram-otp-{id}=param1 )
if the user is on telegram, before every command check for your database (you can cache this), query account table with providerId=telegram & accountId=ctx.from.userId. if both match, then the user is authenticated through both web (user has account on db) and telegram (tg bot is always authed). show them their wallets
if the user is on telegram and does not have an account, you can retry the otp approach. create them a credential account, and ask them to connect their tg on web for the bot to correctly function (then the user will have a credential account and a telegram provider account). If that is too much to ask from the user, after credential sign in, create an account with accountId={tg id} & provider=telegram-bot (differrent from web login). so the user will have both credential account and a tg bot connection account (different from this plugin).

@Re4GD commented on GitHub (Jul 26, 2025): This plugin can partially fix your problem, The telegram user ids are unique so what you can do is: - if the user is on web, make them login with telegram, or link with telegram (this is about this plugin). then tell them that you have a tg bot as well (you can link them to the bot with a start param: t . me/mybot?start=param1, it was something like that. you can use the verification table for creating an otp. verification => telegram-otp-{id}=param1 ) - if the user is on telegram, before every command check for your database (you can cache this), query account table with providerId=telegram & accountId=ctx.from.userId. if both match, then the user is authenticated through both web (user has account on db) and telegram (tg bot is always authed). show them their wallets - if the user is on telegram and does not have an account, you can retry the otp approach. create them a credential account, and ask them to connect their tg on web for the bot to correctly function (then the user will have a credential account and a telegram provider account). If that is too much to ask from the user, after credential sign in, create an account with accountId={tg id} & provider=`telegram-bot` (differrent from web login). so the user will have both credential account and a tg bot connection account (different from this plugin).

GiteaMirror commented

2026-03-13 08:47:08 -05:00

@iatomic1 commented on GitHub (Jul 27, 2025):

Okay man can't wait to use it then
For now just using ott, then when verified i save the session token in redis

@iatomic1 commented on GitHub (Jul 27, 2025): Okay man can't wait to use it then For now just using ott, then when verified i save the session token in redis

GiteaMirror commented

2026-03-13 08:47:09 -05:00

@vitalygashkov commented on GitHub (Aug 7, 2025):

If anyone is interested, I've already implemented a similar plugin: vitalygashkov/telegram-better-auth

@vitalygashkov commented on GitHub (Aug 7, 2025): If anyone is interested, I've already implemented a similar plugin: [vitalygashkov/telegram-better-auth](https://github.com/vitalygashkov/telegram-better-auth)

GiteaMirror commented

2026-03-13 08:47:10 -05:00

@Re4GD commented on GitHub (Aug 30, 2025):

Plugin is almost ready, doing flow tests and writing docs.

Added support for account linking as @iatomic1 requested
Added callbackURLs for identical oauth flows and flexibility
Supports Telegram Login Widget's both callback/redirect flows

The plugin API is exactly like the oauth providers:

export type TelegramOptions = {
  /**
   * Bot token created from BotFather
   */
  botToken: string;
  /**
   * Custom function to map the user profile to a User object.
   */
  mapProfileToUser?: (profile: TelegramProfile) =>
    | {
        id?: string;
        name?: string;
        email?: string | null;
        image?: string;
        emailVerified?: boolean;
        [key: string]: any;
      }
    | Promise<{
        id?: string;
        name?: string;
        email?: string | null;
        image?: string;
        emailVerified?: boolean;
        [key: string]: any;
      }>;
};

@Re4GD commented on GitHub (Aug 30, 2025): Plugin is almost ready, doing flow tests and writing docs. - Added support for account linking as @iatomic1 requested - Added callbackURLs for identical oauth flows and flexibility - Supports Telegram Login Widget's both callback/redirect flows The plugin API is exactly like the oauth providers: ```ts export type TelegramOptions = { /** * Bot token created from BotFather */ botToken: string; /** * Custom function to map the user profile to a User object. */ mapProfileToUser?: (profile: TelegramProfile) => | { id?: string; name?: string; email?: string | null; image?: string; emailVerified?: boolean; [key: string]: any; } | Promise<{ id?: string; name?: string; email?: string | null; image?: string; emailVerified?: boolean; [key: string]: any; }>; }; ```

GiteaMirror commented

2026-03-13 08:47:11 -05:00

@vcode-sh commented on GitHub (Oct 1, 2025):

Hey! I built better-auth-telegram which implements everything requested here:

✅ Telegram Login Widget with callback/redirect flows
✅ Account linking & unlinking
✅ Telegram Mini Apps support (bonus!)
✅ 100% test coverage
✅ Full TypeScript support
✅ Published on npm

npm install better-auth-telegram

GitHub: https://github.com/vcode-sh/better-auth-telegram
Docs: https://github.com/vcode-sh/better-auth-telegram#readme

Feedback welcome!

@vcode-sh commented on GitHub (Oct 1, 2025): Hey! I built `better-auth-telegram` which implements everything requested here: ✅ Telegram Login Widget with callback/redirect flows ✅ Account linking & unlinking ✅ Telegram Mini Apps support (bonus!) ✅ 100% test coverage ✅ Full TypeScript support ✅ Published on npm npm install better-auth-telegram GitHub: https://github.com/vcode-sh/better-auth-telegram Docs: https://github.com/vcode-sh/better-auth-telegram#readme Feedback welcome!

GiteaMirror commented

2026-03-13 08:47:12 -05:00

@mi3lix9 commented on GitHub (Oct 18, 2025):

Hi, I have a strange use case, my bot server is separated from web server, and I want to authorize my users using better auth.

Any one tried to achieve this or has better idea?

@mi3lix9 commented on GitHub (Oct 18, 2025): Hi, I have a strange use case, my bot server is separated from web server, and I want to authorize my users using better auth. Any one tried to achieve this or has better idea?

GiteaMirror commented

2026-03-13 08:47:13 -05:00

@iatomic1 commented on GitHub (Oct 18, 2025):

Like the docs, very engaging😅, Question(tho I prlly know the answer to this) so I'm not using mini apps, just using the telegram bot as is, and there are some commands that needs User being authenticated, but I cannot for the love of God get better auth to run on it, prlly because better auth relies on Web cookies or smthn, does this plugin fixes that? Great plugin btw

Hey! I built better-auth-telegram which implements everything requested here:

✅ Telegram Login Widget with callback/redirect flows
✅ Account linking & unlinking
✅ Telegram Mini Apps support (bonus!)
✅ 100% test coverage
✅ Full TypeScript support
✅ Published on npm

npm install better-auth-telegram

GitHub: https://github.com/vcode-sh/better-auth-telegram
Docs: https://github.com/vcode-sh/better-auth-telegram#readme

Feedback welcome!

@iatomic1 commented on GitHub (Oct 18, 2025): Like the docs, very engaging😅, Question(tho I prlly know the answer to this) so I'm not using mini apps, just using the telegram bot as is, and there are some commands that needs User being authenticated, but I cannot for the love of God get better auth to run on it, prlly because better auth relies on Web cookies or smthn, does this plugin fixes that? Great plugin btw > Hey! I built `better-auth-telegram` which implements everything requested here: > > ✅ Telegram Login Widget with callback/redirect flows > ✅ Account linking & unlinking > ✅ Telegram Mini Apps support (bonus!) > ✅ 100% test coverage > ✅ Full TypeScript support > ✅ Published on npm > > npm install better-auth-telegram > > GitHub: https://github.com/vcode-sh/better-auth-telegram > Docs: https://github.com/vcode-sh/better-auth-telegram#readme > > Feedback welcome!

GiteaMirror commented

2026-03-13 08:47:13 -05:00

@iatomic1 commented on GitHub (Oct 19, 2025):

Hey @vcode-sh i left an issue on the repo

Hey! I built better-auth-telegram which implements everything requested here:

✅ Telegram Login Widget with callback/redirect flows ✅ Account linking & unlinking ✅ Telegram Mini Apps support (bonus!) ✅ 100% test coverage ✅ Full TypeScript support ✅ Published on npm

npm install better-auth-telegram

GitHub: https://github.com/vcode-sh/better-auth-telegram Docs: https://github.com/vcode-sh/better-auth-telegram#readme

Feedback welcome!

@iatomic1 commented on GitHub (Oct 19, 2025): Hey @vcode-sh i left an issue on the repo > Hey! I built `better-auth-telegram` which implements everything requested here: > > ✅ Telegram Login Widget with callback/redirect flows ✅ Account linking & unlinking ✅ Telegram Mini Apps support (bonus!) ✅ 100% test coverage ✅ Full TypeScript support ✅ Published on npm > > npm install better-auth-telegram > > GitHub: https://github.com/vcode-sh/better-auth-telegram Docs: https://github.com/vcode-sh/better-auth-telegram#readme > > Feedback welcome!

GiteaMirror commented

2026-03-13 08:47:14 -05:00

@philippfo9 commented on GitHub (Nov 11, 2025):

Hey! I built better-auth-telegram which implements everything requested here:

✅ Telegram Login Widget with callback/redirect flows ✅ Account linking & unlinking ✅ Telegram Mini Apps support (bonus!) ✅ 100% test coverage ✅ Full TypeScript support ✅ Published on npm

npm install better-auth-telegram

GitHub: https://github.com/vcode-sh/better-auth-telegram Docs: https://github.com/vcode-sh/better-auth-telegram#readme

Feedback welcome!

Do you support the login url for web login to directly login users?

@philippfo9 commented on GitHub (Nov 11, 2025): > Hey! I built `better-auth-telegram` which implements everything requested here: > > ✅ Telegram Login Widget with callback/redirect flows ✅ Account linking & unlinking ✅ Telegram Mini Apps support (bonus!) ✅ 100% test coverage ✅ Full TypeScript support ✅ Published on npm > > npm install better-auth-telegram > > GitHub: https://github.com/vcode-sh/better-auth-telegram Docs: https://github.com/vcode-sh/better-auth-telegram#readme > > Feedback welcome! Do you support the login url for web login to directly login users?

GiteaMirror commented

2026-03-13 08:47:14 -05:00

@dosubot[bot] commented on GitHub (Feb 10, 2026):

Hi, @Re4GD. I'm Dosu, and I'm helping the better-auth team manage their backlog and am marking this issue as stale.

Issue Summary

You proposed adding support for Telegram's Login Widget with its unique OAuth flow and developed a nearly complete plugin.
Your plugin supports account linking, callback URLs, and both callback and redirect flows.
Other contributors shared similar plugins, including vcode-sh's "better-auth-telegram" with advanced features like Mini Apps support and full TypeScript coverage.
The discussion also explored use cases involving Telegram bots connecting with web apps and related authentication challenges.

Next Steps

Please let me know if this issue is still relevant to the latest version of better-auth by commenting here to keep the discussion open.
If I don’t hear back within 7 days, I will automatically close this issue.

Thanks for your understanding and contribution!

@dosubot[bot] commented on GitHub (Feb 10, 2026): Hi, @Re4GD. I'm [Dosu](https://dosu.dev), and I'm helping the better-auth team manage their backlog and am marking this issue as stale. **Issue Summary** - You proposed adding support for Telegram's Login Widget with its unique OAuth flow and developed a nearly complete plugin. - Your plugin supports account linking, callback URLs, and both callback and redirect flows. - Other contributors shared similar plugins, including vcode-sh's "better-auth-telegram" with advanced features like Mini Apps support and full TypeScript coverage. - The discussion also explored use cases involving Telegram bots connecting with web apps and related authentication challenges. **Next Steps** - Please let me know if this issue is still relevant to the latest version of better-auth by commenting here to keep the discussion open. - If I don’t hear back within 7 days, I will automatically close this issue. Thanks for your understanding and contribution!

GiteaMirror commented

2026-03-13 08:47:15 -05:00

@Re4GD commented on GitHub (Feb 16, 2026):

not stale

@Re4GD commented on GitHub (Feb 16, 2026): not stale

GiteaMirror commented

2026-03-13 08:47:17 -05:00

@khashvin commented on GitHub (Mar 4, 2026):

Telegram now supports the standard oauth implementation https://core.telegram.org/bots/telegram-login
I opened a PR implementing it as a social provider #8359

@khashvin commented on GitHub (Mar 4, 2026): Telegram now supports the standard oauth implementation https://core.telegram.org/bots/telegram-login I opened a PR implementing it as a social provider #8359

GiteaMirror referenced this issue

2026-03-13 11:13:56 -05:00

[PR #1436] [CLOSED] feat: allow inviting users to the app #3805

GiteaMirror referenced this issue

2026-04-13 04:01:13 -05:00

[GH-ISSUE #1546] allow admin to invite users #8808

GiteaMirror referenced this issue

2026-04-13 08:09:01 -05:00

[PR #1436] [CLOSED] feat: allow inviting users to the app #12052

GiteaMirror referenced this issue

2026-04-15 15:34:23 -05:00

[GH-ISSUE #1546] allow admin to invite users #17439

GiteaMirror referenced this issue

2026-04-15 19:52:45 -05:00

[PR #1436] [CLOSED] feat: allow inviting users to the app #20706

GiteaMirror referenced this issue

2026-04-17 16:34:32 -05:00

[GH-ISSUE #1546] allow admin to invite users #26131

GiteaMirror referenced this issue

2026-04-17 20:44:44 -05:00

[PR #1436] [CLOSED] feat: allow inviting users to the app #29406

Sign in to join this conversation.

Branches Tags

2026-05-22/chore/adopt-agents-md

2026-05-22/refactor/string-case-utils

dependabot/npm_and_yarn/uuid-14.0.0

dependabot/npm_and_yarn/turbo-2.9.14

changeset-release/main

main

2026-05-14/fix/passkey-verify-error-and-claim

dependabot/npm_and_yarn/samlify-2.13.0

dependabot/npm_and_yarn/ws-8.20.1

changeset-release/next

dependabot/npm_and_yarn/demo/electron/demo-minor-patch-519ef7475f

dependabot/github_actions/github-actions-98f3470200

client-assertions-main

2026-05-15/ci/fix-sqlite-abi-mismatch

2026-05-15/fix/organization-team-add-cascade

2026-05-15/fix/parse-set-cookie-value-validation

2026-05-13/feat/captcha-wildcard-endpoints

2026-05-13/ci/stabilize-docker-startup

fix/i18n-before-hook-translation

fix/disable-migration-generate

2026-05-07/fix/admin-set-password-upsert

2026-05-10/fix/cookie-drain-order

2026-05-10/feat/hooks-finally

2026-05-09/fix/cookie-drain-order

2026-05-09/feat/hooks-finally

2026-05-08/feat/register-before-send

fix/stripe/subscription-data-merge

2026-05-01/chore/pnpm-v11-harden

chore/pnpm-v11

2026-04-29/feat/google-include-granted-scopes

2026-04-29/fix/oauth-account-scope-semantics

2026-04-27/fix/nextcookies-idempotent-writes

2026-04-26/fix/harden-proxy-host-validation

2026-04-26/refactor/stripe-callback-signature-cleanup

2026-04-26/fix/stripe-subscription-callback-timing

2026-04-11/fix/sveltekit-app-modules

feat/open-api-zod-contract

feat/oauth-provider-backchannel-logout-next

feat/oauth-idp-initiated-bounce

refactor/sign-in-challenges

2026-04-21/fix/oauth-rfc-input-validation

fix/release-notes-new-packages

fix/two-factor-identity-guard

fix/resource

feat/emailpassword-authorize

2026-04-12/security/dynamic-baseurl-proxy-trust-default

feat/oauth-provider-at-hash-v2

fix/release-grep-fallback

claude/address-review-comments-JhFLr

claude/slack-update-stripe-docs-consistency-8Sc0w

feat/async-auth

fix/two-factor-totp-verified-enrollment

feat/plugin-ui

codex/blog-1-6-release-post

2026-04-06/fix/type-any-guards

2026-04-05/chore/downgrade-better-call

2026-04-04/ci/skip-vercel-fork-prs

2026-03-28/ci/add-autofix-ci

chore/release-preview-script

himself65/2026/02/19/role

2026-03-24/fix/update-user-info-on-link

2026-03-20/docs/improve-website

2026-03-20/fix/anonymous-onlinkaccount-expo

2026-02-17/fix/anonymous-link-state

fix/8607-saml-inresponseto

fix/8549-scim-patch-noop

v1.4.x

refactor/migration-snapshot-tests

worktree-magic-link-additional-data

chore/migrate-build-to-rollup

worktree-fix-dynamic-baseurl-8447

2026-03-06/chore/public-api-check

fix/close-8156-regression-test

fix/secondary-storage-json-error-handling

himself65/verification-namespace

cursor/issue-8307-validation-79a3

himself65/2026/01/30/error-mdx

v1.4.x-staging

fix/email-otp-user

fix/restrict-full-organization-access-roles

himself65/2026/02/12/count

himself65/2026/02/04/define-plugin

2026-02-04/feat/add-pluralize

cursor/better-auth-js-integration-ec21

cursor/expo-state-mismatch-394c

2026-02-01/fix/org-update-role-sync-members

cursor/issue-7607-investigation-e146

cursor/email-generation-helper-0ff6

himself65/2026/01/21/avoid-spread-operator

himself65/2026/01/14/cli

claude/slack-add-docs-pr-NMvgO

claude/slack-add-advanced-useplural-WHKYL

feat/hooks-pos

feat/2fa-phone

feat/2fa

fix/rotation

fix/username-check

v1.3.x

refactor/organization

feat/multiple-client-ids-social-providers

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/better-auth#1546