Securing Twitter Webhook
As mentioned in Twitter Docs
Steps to validate a request
- Create a hash using your consumer secret and incoming payload body.
- Compare created hash with the base64 encoded x-twitter-webhooks-signature value.
Here is my code for doing so:
const buffer = Buffer.from(JSON.stringify(ctx.request.body))
const expectedHash = crypto.createHmac('sha256', TWITTER_CONSUMER_SECRET).update(buffer).digest('base64')
The x-twitter-webhooks-signature
header from twitter and the hash generated does not match. Also, the post at https://twittercommunity.com/t/validating-the-webhook-signature-header-in-node-js/102525 says that it's JSON.stringify()
issue. I'm using koa and koa-body, how can I fix the hash mismatch?
node.js twitter webhooks koa
add a comment |
As mentioned in Twitter Docs
Steps to validate a request
- Create a hash using your consumer secret and incoming payload body.
- Compare created hash with the base64 encoded x-twitter-webhooks-signature value.
Here is my code for doing so:
const buffer = Buffer.from(JSON.stringify(ctx.request.body))
const expectedHash = crypto.createHmac('sha256', TWITTER_CONSUMER_SECRET).update(buffer).digest('base64')
The x-twitter-webhooks-signature
header from twitter and the hash generated does not match. Also, the post at https://twittercommunity.com/t/validating-the-webhook-signature-header-in-node-js/102525 says that it's JSON.stringify()
issue. I'm using koa and koa-body, how can I fix the hash mismatch?
node.js twitter webhooks koa
add a comment |
As mentioned in Twitter Docs
Steps to validate a request
- Create a hash using your consumer secret and incoming payload body.
- Compare created hash with the base64 encoded x-twitter-webhooks-signature value.
Here is my code for doing so:
const buffer = Buffer.from(JSON.stringify(ctx.request.body))
const expectedHash = crypto.createHmac('sha256', TWITTER_CONSUMER_SECRET).update(buffer).digest('base64')
The x-twitter-webhooks-signature
header from twitter and the hash generated does not match. Also, the post at https://twittercommunity.com/t/validating-the-webhook-signature-header-in-node-js/102525 says that it's JSON.stringify()
issue. I'm using koa and koa-body, how can I fix the hash mismatch?
node.js twitter webhooks koa
As mentioned in Twitter Docs
Steps to validate a request
- Create a hash using your consumer secret and incoming payload body.
- Compare created hash with the base64 encoded x-twitter-webhooks-signature value.
Here is my code for doing so:
const buffer = Buffer.from(JSON.stringify(ctx.request.body))
const expectedHash = crypto.createHmac('sha256', TWITTER_CONSUMER_SECRET).update(buffer).digest('base64')
The x-twitter-webhooks-signature
header from twitter and the hash generated does not match. Also, the post at https://twittercommunity.com/t/validating-the-webhook-signature-header-in-node-js/102525 says that it's JSON.stringify()
issue. I'm using koa and koa-body, how can I fix the hash mismatch?
node.js twitter webhooks koa
node.js twitter webhooks koa
edited Nov 14 '18 at 16:39
dmulter
1,1693917
1,1693917
asked Nov 14 '18 at 7:46
Niket MalikNiket Malik
6801920
6801920
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Found a solution. Used koa-bodyparser
instead of koa-body
then sha256
of ctx.request.rawBody
matches with the header.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53295279%2fsecuring-twitter-webhook%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Found a solution. Used koa-bodyparser
instead of koa-body
then sha256
of ctx.request.rawBody
matches with the header.
add a comment |
Found a solution. Used koa-bodyparser
instead of koa-body
then sha256
of ctx.request.rawBody
matches with the header.
add a comment |
Found a solution. Used koa-bodyparser
instead of koa-body
then sha256
of ctx.request.rawBody
matches with the header.
Found a solution. Used koa-bodyparser
instead of koa-body
then sha256
of ctx.request.rawBody
matches with the header.
answered Nov 15 '18 at 13:31
Niket MalikNiket Malik
6801920
6801920
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53295279%2fsecuring-twitter-webhook%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown