-
-
Notifications
You must be signed in to change notification settings - Fork 963
API 4.3 - Seamless Telegram Login #957
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API 4.3 - Seamless Telegram Login #957
Conversation
This should be good to go, if somebody could add their eyes to check, that would be sweet 💪 @php-telegram-bot/developers |
@noplanman is there any example how to use the seamless telegram login? |
What exactly is your problem? If you don't know how to send the login button to a user/group then this code example might be useful:
Don't forget that you have to link the domain first to your bot or otherwise the login button probably won't work as intended. To link a specific domain to your bot send the The message received by this code example should have a login button beneath it. If the user clicks on it, Telegram will open the specified URL in a browser. The PHP File behind this URL now has to verify the authenticity of the received information. If everything works fine, the user will be logged in on your website. If you are struggling with the authorization part on the web server, I would recommend the official guide for the Telegram Login Widget, because the authorization for the Login Widget works exactly the same way as the Seamless Telegram Login. In fact, if you have already integrated the Telegram Login Widget on your website, you can link the Seamless Login URL to the authorization file from your Login Widget and it will work without any further configuration needed. If you don't know how implement the authorization file itself, I can recommend this code example. I am using the I hope these tips can help you (and everyone else stumbling across this topic). |
@ossiach @noplanman apologize for double post my question. As my comment in #1065 what I’ve got so far:
However, when my page was opened, I see there’s no query string appended to my auth url. It’s just like a normal page, the exact same url I set in LoginUrl. The documentation here talk about messages.acceptUrlAuth and urlAuthResultAccepted but there’s no guide on how to use it. |
Will move this conversation to your initial issue, so others can find the solution more easily... |
Closes #955