-
Notifications
You must be signed in to change notification settings - Fork 851
ssl_context is not passed from async web_client to aiohttp socket client #1304
Copy link
Copy link
Closed
Labels
Version: 3xarea:asyncbugM-T: A confirmed bug report. Issues are confirmed when the reproduction steps are documentedM-T: A confirmed bug report. Issues are confirmed when the reproduction steps are documentedsocket-mode
Milestone
Description
(Filling out the following details about bugs will help us solve your issue sooner.)
Reproducible in:
pip freeze | grep slack
python --version
sw_vers && uname -v # or `ver`The Slack SDK version
3.18.1
Python runtime version
3.8
OS info
Linux version 4.15.0-196-generic (buildd@lcy02-amd64-018) (gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #207-Ubuntu SMP Thu Oct 27 21:24:58 UTC 2022
Expected result:
I expect to be able to provide an SSL context for the websockets to use.
I can provide one to the AsyncWebClient:
AsyncWebClient(token=BOT_TOKEN, ssl=ssl_context)and I want to use the same context for the websocket.
Actual result:
The ssl_context is not passed to ws_connect, which leads to the above error:<urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1076)>
Requirements
For general questions/issues about Slack API platform or its server-side, could you submit questions at https://my.slack.com/help/requests/new instead. 🙇
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Version: 3xarea:asyncbugM-T: A confirmed bug report. Issues are confirmed when the reproduction steps are documentedM-T: A confirmed bug report. Issues are confirmed when the reproduction steps are documentedsocket-mode
