"Invalid Signature" when launch URL has query parameters about ims-lti

[ob1]

@Tape I had the same issue on the Heroku platform where SSL termination occurred before the app, so the app was getting "http" instead of "https".
In that case, heroku adds the "X-Forwarded-Proto" header with the original protocol, which is not standard but very common, so maybe ELB also does.
Knowing that alone doesn't help with signature verification, since the ims-lti code uses req.url directly, so initially I thought to overwrite req.url with the protocol obtained from the header, but I found a better solution.
I'm using Express, and there you can say:

app.enable('trust proxy');

which automagically corrects the url to the original https one.

[Tape]

I actually encountered a similar problem, maybe the ability to provide a custom URL would be the best solution? In my case I am using SSL termination on an Amazon ELB so the detected url is http, not https, thus causing the signature to be invalid.

[Tape]

Oh duh, I feel dumb now. Thank you for that! If I get time today I'll take a look at the query params, I know oauth treats them specially.