Moves HMAC validation from using the shorter sha1 value to the now provided sha256 value
Description
Move from using:
X-Hub-Signature: sha1=7d38cdd689735b008b3c702edd92eea23791c5f6
To using:
X-Hub-Signature-256: sha256=d57c68ca6f92289e6987922ff26938930f6e66a2d161ef06abdf1859230aa23c
Motivation and Context
Fixes #181
[x] An issue is open that proposes this change (required)
How Has This Been Tested?
~Looks like the build is failing on account of modules too.~ resolved
Initial test to trigger the error message - no header is supplied through this route.
Use valid Derek command to test it is processed correctly
Signed-off-by: Richard Gee richard@technologee.co.uk
Moves HMAC validation from using the shorter sha1 value to the now provided sha256 value
Description
Move from using:
X-Hub-Signature: sha1=7d38cdd689735b008b3c702edd92eea23791c5f6
To using:X-Hub-Signature-256: sha256=d57c68ca6f92289e6987922ff26938930f6e66a2d161ef06abdf1859230aa23c
Motivation and Context
Fixes #181
How Has This Been Tested?
~Looks like the build is failing on account of modules too.~ resolved
Initial test to trigger the error message - no header is supplied through this route.
Use valid Derek command to test it is processed correctly
this is the test repo/issue
View of associated Github payload delivery
And the function logs:
Types of changes
Checklist:
git commit -s