mattermost / mattermost/mattermost-plugin-github
Plugin should avoid using revoked tokens
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 179
- Forks
- 180
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 13
Description
If we perform an API request using a user's token, and we receive a response noting that the token is revoked, we should:
- delete the token from the KV store, declaring the user as disconnected
- and notify the user via DM that their token has been revoked, and that they will need to reconnect their account in order to use the plugin
cc @aaronrothschild for this approach
_Issue created from a [Mattermost message](https://community-daily.mattermost.com/_redirect/pl/px91jzxiqpy68kzrhperatxcth) *by `@thiefmaster`*._
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the GitHub API request path and the token KV-store handling, then trace how disconnected users are represented and how direct messages are sent. Done means revoked tokens are deleted, the user is marked disconnected, and the user receives a reconnection notice.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go
- Domain
- api, authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100