[SOLVED] Can't Set Extension Required Configuration

Cynthia · September 9, 2017, 5:27pm

Hello!

I am trying to make an extension that requires configuration, I have set the “Required Configurations” field in Extensions Capabilities (current value is: this_is_a_test)…

In my config javascript file, in the onAuthorized event, I send the auth.token to my EBS, which I can confirm that I receive succesfully. When the user click on “Submit” in the config.html, I send an AJAX request to my EBS and I have to send the PUT request https://dev.twitch.tv/docs/extensions/reference#set-extension-required-configuration … but this is where I am stuck. It looks like I can’t sign the JWT token properly, I am using https://github.com/auth0/node-jsonwebtoken to sign it, this is my code to sign the token:

jwt.sign({
    "exp": Math.floor(Date.now() / 1000) + (60 * 60),
    "user_id": payload.user_id,
    "role": "external"
}, "my-secret-key");

FYI: I did console.log(payload) and console.log(payload.user_id) to make sure it is a valid payload and user_id.

It returns a signed token and when I try to send it in the header, I get {“code”:401,“status”:“authentication failed”}

I modified a little bit my code (changed client ID, secret, etc…):

const signed = jwt.sign({
    "exp": Math.floor(Date.now() / 1000) + (60 * 60),
    "user_id": payload.user_id,
    "role": "external"
}, "sOmESecReT=");

require("request")({
    url: "https://api.twitch.tv/extensions/s0m3cl1entid/0.0.1/oauth_receipt?channel_id=" + payload.channel_id,
    method: "PUT",
    headers: {
        "Authorization": "Bearer " + signed,
        "Client-Id": "s0m3cl1enTid"
    },
    json: {
        "required_configuration": "this_is_a_test"
    }
}, function(err, res) {
    console.log(err, res.body);
});

Anyone know what I am missing here ? I even tested with Postman and still no luck. I can confirm that I can decode my signed token using jwt.decode.

Thanks

WebFreak · September 9, 2017, 6:16pm

I think you need to use the user_id of the extension owner (your own one, as string). Also did you base64 decode the secret you get from the extension page? For me authentication only worked after decoding it and signing using the decoded key, though I am not using node.js so I can’t help you on how to do that, check the readme of your jwt library.

Cynthia · September 9, 2017, 6:26pm

I just tried with:

new Buffer(“sOmESecReT=”).toString()
and
new Buffer(“sOmESecReT=”).toString(“utf8”)
and
new Buffer(“sOmESecReT=”).toString(“base64”)

Still no luck, as for the user_id, thanks for pointing this out. At the moment, the user_id is mine as I am testing locally with my Twitch account

I read the whole JWT library docs and can’t seem to find the reason why it’s not working

WebFreak · September 9, 2017, 6:30pm

I quickly looked at the readme, try passing new Buffer('extension_SecReT=', 'base64') as secret. It doesn’t say anywhere on the sign doc, but on the verify doc https://github.com/auth0/node-jsonwebtoken#jwtverifytoken-secretorpublickey-options-callback

Cynthia · September 9, 2017, 6:33pm

Still no luck I just tried to generate a new secret, still doesn’t work with and without base64 decode

BarryCarlyon · September 9, 2017, 7:21pm

You have the wrong type on your user_id needs to be a string not a numeric/integer.
Try this:

var secret = Buffer.from('sOmESecReT=', 'base64');

var tokenPayload = {
    exp: Math.floor(new Date().getTime() / 1000) + 60,
    channel_id: ''+channel_id,
    role: 'external',

    pubsub_perms: {
        send: [
            'broadcast'
        ]
    }
}

let signedJwt = jwt.sign(tokenPayload, secret);

base64decode the secret before use.
And cast the user_id and/or channel ID’s to strings not numerics. Note the explicit ''+channel_id in my example.

Above is a snippet from my pubsub sender as apposed to the oauth_receipt which I have not tested with.

Cynthia · September 9, 2017, 7:31pm

I think the mistake was with the way I was decoding the secret, I tried with new Buffer.from(“sOmESecReT=”, “base64”); instead of new Buffer(“sOmESecReT=”).toString(“base64”) and now I have a new error (that I will be able to fix): The broadcaster has not tried to activate this extension

So I guess this solved the issue, thank you <3

BarryCarlyon · September 9, 2017, 7:43pm

Hah, yeah now I look properly you were encoding it instead of decoding it…

Cynthia · September 10, 2017, 2:49pm

Actually, what would cause “The broadcaster has not tried to activate this extension” response? I thought this endpoint was to enable the activation of the extension, of course the broadcasted has not tried to activate the extension yet! … Anyone can explain ? Maybe I should create another topic for this actually.

BarryCarlyon · September 11, 2017, 6:46am

A broadcaster will install an extension.

Then a broadcaster will activate it into a panel/overlay slot.

When installed, the caster has access to the configuration panels

Cynthia · September 11, 2017, 12:38pm

Oh okay, so I got the wrong endpoint then? At the moment, when you install the extension, you HAVE to configure it first as it says “Needs Configuration” instead of “Activate” (That is what I want). Once the broadcaster sends the configuration, I am sending the PUT request to enable the activation, so that the broadcaster can go back and instead of seeing “Needs Configuration”, he would see the “Activate” button.

BarryCarlyon · September 11, 2017, 1:16pm

You got it!