fix(slack): remove redundant token parameter causing manual auth prompts - #124
Merged
michaelelrom merged 1 commit intoSep 17, 2026
Conversation
Every operation already authenticates via the botToken security scheme (components.securitySchemes.botToken, http/bearer). The per-operation `token` parameter (header on write operations, query on several read operations) duplicated that, causing platform to expect a token input on every task instead of relying on the configured integration credential.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
tokenparameter (header or query, depending on the operation) from all 60 operations that had onebotTokensecurity scheme (http/bearer) declared globally — this parameter was a leftover duplicate from the vendor's original per-method docsTest plan
botTokenwith a real Slack bot tokenchat.postMessage— succeeded without any per-task token input, using only the integration's configured credential