Skip to content

Instantly share code, notes, and snippets.

What would you like to do?
Telegram website login widget, signature check sample using Node.js
// Copied by,
// thanks for improving code style
const { createHash, createHmac } = require('crypto');
const TOKEN = "ABC:12345...";
// I prefer get the secret's hash once but check the gist linked
// on line 1 if you prefer passing the bot token as a param
const secret = createHash('sha256')
function checkSignature ({ hash, }) {
const checkString = Object.keys(data)
.map(k => (`${k}=${data[k]}`))
const hmac = createHmac('sha256', secret)
return hmac === hash;
// Sample usage
const payload = {
id: '424242424242',
first_name: 'John',
last_name: 'Doe',
username: 'username',
photo_url: '',
auth_date: '1519400000',
hash: '87e5a7e644d0ee362334d92bc8ecc981ca11ffc11eca809505'
Copy link

Pitasi commented Oct 29, 2020

I'm not sure. Is it possible that you are receiving requests that are not from Telegram? Did you make any change to my code?

Copy link

rbeer commented Jan 15, 2022

Did you actually use this token const TOKEN = "ABC:12345..."; to create the hash in payload?
The example as it is doesn't work for me. It works as soon as I use real data, i.e. a live response from Telegram and my own bot token.
I think people merely copy/pasting and expecting this to work is what leads to confusion.

Replace payload.hash with fdd4901b22ee5ea34d77caeac88b5ecba818226ab9c7c7775c8ff675d7e4cb92 and this example works.

I think the gist you copied this from always used some made-up value for the hash, to begin with. Even the length doesn't add up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment