# Login with Telegram

**URL:** https://meta.discourse.org/t/login-with-telegram/80046
**Category:** Feature
**Created:** [February 7, 2018, 7:33pm UTC](https://meta.discourse.org/t/login-with-telegram/80046 "2018-02-07T19:33:55Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![barreeeiroo](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/barreeeiroo/32/165264_2.png) [@barreeeiroo](https://meta.discourse.org/u/barreeeiroo)
#### Post date: [February 7, 2018, 7:33pm UTC](https://meta.discourse.org/t/login-with-telegram/80046/1 "2018-02-07T19:33:56Z")

</div>

Are there any plans for integrating Telegram Login as an OAuth provider? Or someone that could do a plugin? 😅

It has been released today, I tested and it’s really practical:

> **[Telegram Login for Websites](https://telegram.org/blog/login)**
>
> The Login Widget offers a frictionless way to authorize users on your website and ask for permission to contact them on Telegram.

---

<div class="post-metadata">

### Author: ![barreeeiroo](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/barreeeiroo/32/165264_2.png) [@barreeeiroo](https://meta.discourse.org/u/barreeeiroo)
#### Post date: [February 7, 2018, 8:04pm UTC](https://meta.discourse.org/t/login-with-telegram/80046/2 "2018-02-07T20:04:22Z")

</div>

I attach some screenshots of how it works:

 ![chrome](https://global.discourse-cdn.com/meta/original/3X/6/b/6bc4caa764a074d5d71dd08dc41094d9168f8f0c.png) ![beta](https://global.discourse-cdn.com/meta/original/3X/9/a/9aa64140cf324978f733a4cea78eb0219e4e50c7.png) ![chrome](https://global.discourse-cdn.com/meta/original/3X/0/d/0d93a919db01eebcc483c2c13f3649af68c9284a.png) ![beta](https://global.discourse-cdn.com/meta/original/3X/4/0/4067d9fb99cba29d2a5b2874715ba016712b340a.png) ![chrome](https://global.discourse-cdn.com/meta/original/3X/0/5/05fcb7930a616c4c77578e7194eb5a2cbe039ba6.png) ![chrome](https://global.discourse-cdn.com/meta/original/3X/8/7/871550a83ba3519477ebc14bf19e42738e9cc777.png)

---

<div class="post-metadata">

### Author: ![Hector](https://avatars.discourse-cdn.com/v4/letter/h/43a26b/32.png) [@Hector](https://meta.discourse.org/u/Hector)
#### Post date: [February 7, 2018, 9:35pm UTC](https://meta.discourse.org/t/login-with-telegram/80046/3 "2018-02-07T21:35:18Z")

</div>

> [@barreeeiroo](#):
>
> Are there any plans for integrating Telegram Login as an OAuth provider?

To be precise it’s not an implementation of the oauth protocol. Very interesting anyway.

---

<div class="post-metadata">

### Author: ![kirushik](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/kirushik/32/102835_2.png) [@kirushik](https://meta.discourse.org/u/kirushik)
#### Post date: [April 8, 2018, 11:46am UTC](https://meta.discourse.org/t/login-with-telegram/80046/4 "2018-04-08T11:46:48Z")

</div>

By the way, I’ve implemented [Discourse SSO](https://meta.discourse.org/t/13045?silent=true) provider for Telegram Login, basing on the code from my [SAML SSO provider](https://meta.discourse.org/t/saml-authentication-proxy-for-discourse-sso/27864):

[https://github.com/kirushik/discourse\_telegram\_auth/](https://github.com/kirushik/discourse_telegram_auth/)

Also available from DockerHub, `docker pull kirushik/discourse_telegram_auth`.

Currently it’s completely untested, and lacks any documentation — but bugreports and feature requests are welcome.

---

<div class="post-metadata">

### Author: ![barreeeiroo](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/barreeeiroo/32/165264_2.png) [@barreeeiroo](https://meta.discourse.org/u/barreeeiroo)
#### Post date: [April 8, 2018, 8:16pm UTC](https://meta.discourse.org/t/login-with-telegram/80046/5 "2018-04-08T20:16:23Z")

</div>

Any preview or demo? 😅

---

<div class="post-metadata">

### Author: ![kirushik](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/kirushik/32/102835_2.png) [@kirushik](https://meta.discourse.org/u/kirushik)
#### Post date: [April 10, 2018, 8:28am UTC](https://meta.discourse.org/t/login-with-telegram/80046/6 "2018-04-10T08:28:44Z")

</div>

Well, it’s available on the forum I’ve written it for — but it’s a special-interest group in Russian, so I don’t think sharing it here will be a good idea.

Meanwhile, using Telegram as SSO provider is not what most people want — so I think I’d spend some time turning my code in a proper auth plugin…

---

<div class="post-metadata">

### Author: ![BobbyZopfan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bobbyzopfan/32/149374_2.png) [@BobbyZopfan](https://meta.discourse.org/u/BobbyZopfan)
#### Post date: [May 17, 2019, 9:45am UTC](https://meta.discourse.org/t/login-with-telegram/80046/7 "2019-05-17T09:45:44Z")

</div>

> [@kirushik](#):
>
> available on the forum I’ve written it for — but it’s a special-interest group in Russian, so I don’t think sharing it here will be a good idea.
> 
> Meanwhile, using Telegram as SSO prov

It would be great if something like that could be implemented. I.e. login/signup on Discourse site thru telegram.  
I’ve found that normal users are not able to login/signup to my forum simply because they never remember their emails ID and PWs. They just get someone to create an email account when they setup their new android phone, and then afterwards they never sign out or sign in to the same.

---

<div class="post-metadata">

### Author: ![Bathinda](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bathinda/32/135888_2.png) [@Bathinda](https://meta.discourse.org/u/Bathinda)
#### Post date: [November 30, 2019, 10:51am UTC](https://meta.discourse.org/t/login-with-telegram/80046/8 "2019-11-30T10:51:51Z")

</div>

Any progress there, just in case?  
I was interested in making our site users to be able to create account and login thru telegram. This way they can dispense with email id/pw, and can create account and login with just their mobile number (and telegram app).

---

<div class="post-metadata">

### Author: ![sunjam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sunjam/32/175682_2.png) [@sunjam](https://meta.discourse.org/u/sunjam)
#### Post date: [March 24, 2020, 7:19pm UTC](https://meta.discourse.org/t/login-with-telegram/80046/9 "2020-03-24T19:19:52Z")

</div>

I’m also curious on this. Has anyone set it up successfully? I see [both forks](https://github.com/kirushik/discourse_telegram_auth/network/members) have not received updates since April of 2018.

---

<div class="post-metadata">

### Author: ![Terrapop](https://avatars.discourse-cdn.com/v4/letter/t/ecd19e/32.png) [@Terrapop](https://meta.discourse.org/u/Terrapop)
#### Post date: [March 10, 2021, 8:39pm UTC](https://meta.discourse.org/t/login-with-telegram/80046/11 "2021-03-10T20:39:41Z")

</div>

Would love to see this working, we have over 200,000 subscribers on Telegram and this would help us a lot.

---

<div class="post-metadata">

### Author: ![tachibanalolo](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tachibanalolo/32/233762_2.png) [@tachibanalolo](https://meta.discourse.org/u/tachibanalolo)
#### Post date: [October 11, 2021, 3:38pm UTC](https://meta.discourse.org/t/login-with-telegram/80046/12 "2021-10-11T15:38:09Z")

</div>

Love this project, is it still going well?

---

<div class="post-metadata">

### Author: ![kirushik](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/kirushik/32/102835_2.png) [@kirushik](https://meta.discourse.org/u/kirushik)
#### Post date: [October 11, 2021, 3:53pm UTC](https://meta.discourse.org/t/login-with-telegram/80046/13 "2021-10-11T15:53:46Z")

</div>

Well, the code is still there, and nothing should be _broken_ in it (give or take the outdated and potentially vulnerable dependencies).  
I no longer believe that abusing Discourse’s SSO APIs for logging in with Telegram is the right way to go, though (thus the repo is archived).

Much better solution would be a plugin adding a Telegram button to the supported auth options on the login popup/screen — but this would require quite a different approach, and I’m not aware of anyone trying to do this (even if it is 100% possible, and I remember seeing other plugins with similar functionality using other login networks somewhere out there)

---

<div class="post-metadata">

### Author: ![mjsir911](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mjsir911/32/264466_2.png) [@mjsir911](https://meta.discourse.org/u/mjsir911)
#### Post date: [October 15, 2022, 8:35pm UTC](https://meta.discourse.org/t/login-with-telegram/80046/15 "2022-10-15T20:35:49Z")

</div>

I’ve got a v1 up and running here:

[https://github.com/mjsir911/discourse-telegram-auth](https://github.com/mjsir911/discourse-telegram-auth)

---

<div class="post-metadata">

### Author: ![downloadwhats\_tatus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/downloadwhats_tatus/32/271997_2.png) [@downloadwhats\_tatus](https://meta.discourse.org/u/downloadwhats_tatus)
#### Post date: [October 21, 2022, 5:17am UTC](https://meta.discourse.org/t/login-with-telegram/80046/17 "2022-10-21T05:17:29Z")

</div>

![image](https://global.discourse-cdn.com/meta/original/4X/9/b/f/9bf3ffce071c5b7b7bdc8475ef4830bc302f4602.png)  
I am getting problem

signature mismatch faliure in signup

---

<div class="post-metadata">

### Author: ![Mr.X\_Mr.X](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mr.x_mr.x/32/126610_2.png) [@Mr.X\_Mr.X](https://meta.discourse.org/u/Mr.X_Mr.X)
#### Post date: [December 18, 2022, 2:03pm UTC](https://meta.discourse.org/t/login-with-telegram/80046/18 "2022-12-18T14:03:55Z")

</div>

@mjsir911 do you intend to continue working on this plug-in? Besides the issues mentioned in the github rep that would be great to have the ability to fetch the uniqueid and not the Name field, and the username. Useful for a future flow. I can set it as a job in the #Marketplace if anyone is up for it.

---

<div class="post-metadata">

### Author: ![Aizada\_M](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/aizada_m/32/352050_2.png) [@Aizada\_M](https://meta.discourse.org/u/Aizada_M)
#### Post date: [November 15, 2023, 1:10pm UTC](https://meta.discourse.org/t/login-with-telegram/80046/19 "2023-11-15T13:10:26Z")

</div>

Hello! I want to thank @mjsir911 for the much-needed and wonderful plugin 🙌

> [@Mr.X\_Mr.X](#):
>
> @mjsir911 do you intend to continue working on this plug-in? Besides the issues mentioned in the github rep that would be great to have the ability to fetch the uniqueid and not the Name field, and the username. Useful for a future flow. I can set it as a job in the #Marketplace if anyone is up for it.

I agree with you @Mr.X_Mr.X. I also wanted to ask @mjsir911 how can I remove the line for entering an email address when registering through a Telegram bot? In my case, I chose this plugin so that people don’t have to go through extra steps (especially entering their email address) to register. When I was going to install this plugin, I was sure that email would not be requested ☹

---

<div class="post-metadata">

### Author: ![ErlendMS](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/erlendms/32/355598_2.png) [@ErlendMS](https://meta.discourse.org/u/ErlendMS)
#### Post date: [January 20, 2024, 2:44pm UTC](https://meta.discourse.org/t/login-with-telegram/80046/20 "2024-01-20T14:44:54Z")

</div>

I got it to work! 🙌🏻

But, when I click “Log in with Telegram” on Discourse, I get sent to _**[mysite.com/auth/telegram](http://mysite.com/auth/telegram)**_ - and it looks like this:

 ![lørdag, 20 jan. 2024 15:39:19](https://global.discourse-cdn.com/meta/original/4X/4/3/d/43da78da93e6b382dfe1a8680659b874c0b39589.jpeg)

**Do you know if that site is set from the plugin or what?** I can’t edit the CSS either, as the page is outside the scope of themes…

---

<div class="post-metadata">

### Author: ![Mr.X\_Mr.X](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mr.x_mr.x/32/126610_2.png) [@Mr.X\_Mr.X](https://meta.discourse.org/u/Mr.X_Mr.X)
#### Post date: [March 11, 2024, 7:14pm UTC](https://meta.discourse.org/t/login-with-telegram/80046/21 "2024-03-11T19:14:49Z")

</div>

Is this still working? I don’t get the login button anymore

---

<div class="post-metadata">

### Author: ![Mr.X\_Mr.X](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mr.x_mr.x/32/126610_2.png) [@Mr.X\_Mr.X](https://meta.discourse.org/u/Mr.X_Mr.X)
#### Post date: [March 28, 2024, 3:08am UTC](https://meta.discourse.org/t/login-with-telegram/80046/22 "2024-03-28T03:08:08Z")

</div>

I have troubles with making this work, can someone update if it’s working?

---

<div class="post-metadata">

### Author: ![DigneZzZ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dignezzz/32/506171_2.png) [@DigneZzZ](https://meta.discourse.org/u/DigneZzZ)
#### Post date: [June 8, 2025, 5:28pm UTC](https://meta.discourse.org/t/login-with-telegram/80046/24 "2025-06-08T17:28:52Z")

</div>

Hi folks, I’ve been trying to redesign the plugin too, but no luck.  
This old version of the plugin also does not work.  
I guess I’ll have to find someone to write it from scratch…  
For me it is fundamentally important that all accounts have mandatory authorization and confirmed login via Telegram. If anyone knows the solution - please write.
