Skip to content

Issues signing incoming slash command requests (Flask) #41

@wooddar

Description

@wooddar

Description

I have been trying to use the verify_signature function from the events server to securely authenticate slash command requests. The issue here is that the Flask request body is coming up as empty bytes for a slash command b'' where the actual slash command data is form encoded.

It would be great to have some guidance as to how to verify the signature of incoming slash command requests in Flask as I am currently having to rely on token authentication. Please let me know if anymore details are required.

@aoberoi

What type of issue is this? (place an x in one of the [ ])

  • bug
  • enhancement (feature request)
  • question
  • documentation related
  • testing related
  • discussion

Requirements

  • I've read and understood the Contributing guidelines and have done my best effort to follow them.
  • I've read and agree to the Code of Conduct.
  • I've searched for any related issues and avoided creating a duplicate issue.

Reproducible in:

slackeventsapi version: latest
Flask version: 1.0.2
OS version(s): N/A

Steps to reproduce:

  1. Call the verify_signature function from a slash command request context

Expected result:

Signed secret successfully reproduced from the request body

Actual result:

Error is raised as request content/json is blank

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions