Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Store S3 bucket secret in KV store #63

Closed
wants to merge 7 commits into from
Closed

Conversation

mickmister
Copy link
Contributor

Summary

This PR makes it so when the admin submits the custom S3 bucket settings, we store it in the KV store, and store a string of asterisks in the server config. This is so we never expose the saved secret to the client later.

This PR also requires upgrading the MM server dependency. ATM this PR sets it to a very recent version, though it only needs to be up to 8.0 for the ConfigurationWillBeSaved hook.

Ticket Link

Fixes #54

@mickmister mickmister requested a review from fmartingr June 11, 2024 06:51
@mickmister mickmister changed the title Encrypt S3 bucket secret in KV store Store S3 bucket secret in KV store Jun 11, 2024
server/plugin.go Outdated Show resolved Hide resolved
@mickmister mickmister marked this pull request as ready for review June 25, 2024 05:54
github.com/mattermost/mattermost-server/v6 v6.0.0-20221012175353-8cb6718a9bcc
github.com/mattermost/mattermost/server/public v0.0.9
github.com/mattermost/mattermost/server/public v0.1.4
github.com/mattermost/mattermost/server/v8 v8.0.0-20240610152044-b86ba51efd4f
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Flagging this from our conversation yesterday. @wiggin77

@hanzei hanzei added the 2: Dev Review Requires review by a core committer label Jul 4, 2024
@mickmister mickmister closed this Jul 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2: Dev Review Requires review by a core committer
Projects
None yet
Development

Successfully merging this pull request may close these issues.

S3 bucket creds should be encrypted in transport to client
3 participants