-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid signatures with django-ask-sdk since ask-sdk-webservice-support v1.3.3 #202
Comments
Added verify_signature=False to SkillAdapter initialization as a workaround for a bug mentioned here: alexa/alexa-skills-kit-sdk-for-python#202
Encountering the same issue here. |
Updates the Django-specific signature header to use SHA-256 rather than SHA-1 Fixes alexa#202
Bugfix for this is in PR #207 While waiting for that to get merged, I've created a custom package that wraps up the fix. If you want to use it, just copy the following into your requirements.txt instead of
Note - I will delete this repo once the fix is officially released, so if you use it make a note to change it back later! |
my observation
if i disable to verifier in file it then launches the app update: downgrading to 1.3.2 works |
I'm submitting a...
Expected Behavior
Request signatures should validate when using django-ask-sdk
Current Behavior
I'm using django-ask-sdk for a Django-hosted Alexa skill. Since ask-sdk-webservice-support v1.3.3, all incoming requests to the Alexa endpoint cause a
InvalidSignature
exception.Possible Solution
The problem appears since ask-sdk-webservice-support v1.3.3 and disappears again by going back to v1.3.2. The problem seams to be related to ask-sdk-webservice-support's
RequestVerifier
class is now using SHA256 instead of SHA1 ashash_algorithm
by default:and django-ask-sdk's
SkillAdapter
class is using the default value forhash_algorithm
when instantiating the RequestVerifier:Steps to Reproduce (for bugs)
pip install Django django-ask-sdk
Context
Your Environment
Python version info
3.9.2
The text was updated successfully, but these errors were encountered: