-
Notifications
You must be signed in to change notification settings - Fork 150
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
[MM-57194] Mark confidential settings as secrets #811
Conversation
f3d7ee4
to
65fa789
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR has been tested with the help of mattermost/mattermost#27986 as it requires some changes in the server.
All the secrets and keys are shown encrypted in the plugin settings, LGTM. Approved.
Summary
Make use of mattermost/mattermost#27986 by marking the following config settings as secrets:
GitHubOAuthClientSecret
WebhookSecret
EncryptionKey
The other changes are needed due to the breaking changes in mattermost/mattermost#26471.
GitHubOAuthClientID
is shown in plain text in the GitHub UI, so I don't think it needs to be obfuscated.Ticket Link
https://mattermost.atlassian.net/browse/MM-57194