-
Notifications
You must be signed in to change notification settings - Fork 24
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
Check Signature of Request #1
Comments
I'll pick this up now 👍 already got a partial implementation |
Awesome @mattrayner , thanks so much! |
Hi @sjmog, There was already a gem with partial functionality available here: I've been in contact with @sidoh about merging our efforts back into his alexa_verifier gem. In the meantime I have a PR open on my own gem at: If you're happy with the above I'll begin some integration work? Did you have any thoughts here or are you happy for me to just 'have at it'? |
Following on from the above message, alexa_request_verifier has now been merged into alexa_verifier and I will begin work on integrating it into ralyxa shortly |
Awesome – thank you @mattrayner Both your verifier and @sidoh's verifier look super-reasonable to me. Would you be happy to do a doc update to Ralyxa's README, too? |
Definitely - I’m in the process of integrating it directly into Ralyxa with
a config block to toggle the verification - once I’ve done that I’ll create
a PR
…On Mon, 4 Dec 2017 at 10:29 Sam Morgan ***@***.***> wrote:
Awesome – thank you @mattrayner <https://github.com/mattrayner>
Both your verifier <https://github.com/mattrayner/alexa_request_verifier>
and @sidoh <https://github.com/sidoh>'s verifier
<https://github.com/sidoh/alexa_verifier> look super-reasonable to me.
Would you be happy to do a doc update to Ralyxa's README, too?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ADVzNuW29HMTkYb4zbuXHl_oBOP8Pkn8ks5s88mYgaJpZM4OG48P>
.
|
Closed by #3 |
Users of this gem should be able to configure signature-checking through it as painlessly as possible.
There is an NPM Package which does this for node-based Alexa skills.
The text was updated successfully, but these errors were encountered: