Problem Statement
For corporate internal slack applications, socket mode is a huge life saver to have. Corporate firewalls make it very very tough to get endpoints that are fully exposed to the public internet, preventing those of us who work in more security centric domains from using this SDK for our internal slack bot applications.
Proposed Solution
A new socketMode: boolean parameter added to the SlackAdapterConfig that would allow the underlying transport of the slack adapter to be socket mode instead of HTTP mode. This is thoroughly well documented in Slack’s bolt framework - so enough context for an agent to get it right might be easier than implementing from scratch.
Since the adapter interface is transport agnostic enough it seems - hopefully the code change wouldn’t be too bad.
Alternatives Considered
No response
Use Case
import { Chat } from “chat”
import { createSlackAdapter } from “@chat-adapter/slack”
const bot = new Chat({
adapters: {
slack: createSlackAdapter({
socketMode: true,
// …
})
},
// …
})
Priority
Critical
Contribution
Additional Context
No response
Problem Statement
For corporate internal slack applications, socket mode is a huge life saver to have. Corporate firewalls make it very very tough to get endpoints that are fully exposed to the public internet, preventing those of us who work in more security centric domains from using this SDK for our internal slack bot applications.
Proposed Solution
A new
socketMode: booleanparameter added to theSlackAdapterConfigthat would allow the underlying transport of the slack adapter to be socket mode instead of HTTP mode. This is thoroughly well documented in Slack’s bolt framework - so enough context for an agent to get it right might be easier than implementing from scratch.Since the adapter interface is transport agnostic enough it seems - hopefully the code change wouldn’t be too bad.
Alternatives Considered
No response
Use Case
Priority
Critical
Contribution
Additional Context
No response