Slash comamnd 401 Unauthorized - slack_bolt_receiver_authenticity_error

Description

Was trying to add slash command to the bot using /slack/events as request url in the app config

But bolt-js response 401 for the ssl_check

It seems its doing verify signature first before response to ssl

But the POST request from Slack doesn’t have signature in the header

So, How can I add slash command and what should its request url be?

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

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

Requirements (place an x in each of the [ ])

• 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.

---

Bug Report

Filling out the following details about bugs will help us solve your issue sooner.

Reproducible in:

package version:

node version:

OS version(s):

Steps to reproduce:

1. Add a new slash command with url /slack/events
2. App returns 401 unauthorized

Expected result:

Should pass the ssl_check

Actual result:

Not pass the ssl_check instead it’s trying to verify the signature

Attachments:

App output

The request

[dhinson919]

This answer may be too late but it might help others. The SLACK_SIGNING_SECRET environment variable is not set correctly for your app. See section ‘Adding your app credentials’ at https://api.slack.com/start/building/bolt-python for an example.

[seratch]

Hi all in this conversation, I’ve revisited this issue and it seems that we, the SDK maintainers, have provided answers to each question. Thus, let us close this one for now.

If you have a question similar to this topic, please feel free to create a new one with detailed information. We are happy to help you out 👋