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:
21 个赞
To be precise it’s not an implementation of the oauth protocol. Very interesting anyway.
2 个赞
By the way, I’ve implemented Discourse SSO provider for Telegram Login, basing on the code from my SAML SSO provider:
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.
10 个赞
Any preview or demo?
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…
4 个赞
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.
1 个赞
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).
I’m also curious on this. Has anyone set it up successfully? I see both forks have not received updates since April of 2018.
1 个赞
Would love to see this working, we have over 200,000 subscribers on Telegram and this would help us a lot.
1 个赞
Love this project, is it still going well?
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)
4 个赞
我这里有一个v1版本：
8 个赞
@mjsir911 您打算继续处理这个插件吗？除了 GitHub 仓库中提到的问题之外，能够获取唯一 ID 而不是名称字段以及用户名将会很棒。这对于未来的流程很有用。如果有人愿意，我可以将其设置为 Marketplace 中的一个任务。
2 个赞
你好！我想感谢@mjsir911 提供了这个急需且很棒的插件 
我同意你的看法@Mr.X_Mr.X。我还想问@mjsir911，如何在我通过Telegram机器人注册时删除输入电子邮件地址的选项？在我的例子中，我选择这个插件是为了让人们不必经过额外的步骤（尤其是输入电子邮件地址）来注册。当我准备安装这个插件时，我确信它不会要求提供电子邮件 
我搞定了！
但是，当我点击 Discourse 上的“使用 Telegram 登录”时，我会跳转到 mysite.com/auth/telegram - 并且看起来是这样的：
**您知道那个网站是由插件设置的还是什么吗？**我也无法编辑 CSS，因为该页面超出了主题的范围……
这还奏效吗？我再也看不到登录按钮了
我无法使其正常工作，有人可以更新一下它是否有效吗？
1 个赞
各位好，我也一直在尝试重新设计这个插件，但没有成功。
这个旧版本的插件也无法工作。
我想我必须找人从头开始编写了……
对我来说，所有账户都必须强制授权并通过 Telegram 确认登录这一点至关重要。如果有人知道解决方案，请写下来。