-
Notifications
You must be signed in to change notification settings - Fork 23
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
Add at-rest encryption for OAuth2 token #14
Comments
@levb I am taking this one, just to get going with dev setup for this plugin mainly. |
Hi @gopheros are you still interested in working on this ticket? |
Hello @levb, Yeah will provide a PR in couple of days. Thanks |
Hi @gopheros ! How are you doing? If you are not able to continue working on this, please let us know, so we can mark it as up for grabs for other contributor. Thanks! |
Hello @larkox , I can continue work on this. |
Hi @gopheros ! How are you? What do you think? |
Hi @gopheros . I will take this. Thank you very much for your interest and your contributions. |
* Add at-rest encryption for OAuth2 token * Fix test * Fix lint Co-authored-by: Lev <[email protected]>
Presently, the POC code stores the OAuth token(s) unencrypted. It is a best practice to have it encrypted when stored persistently, so that the encryption keys may (eventually) be stored separately.
This improvement is currently pending to the Zoom plugin, can copy from there, https://github.com/mattermost/mattermost-plugin-zoom/pull/52/files, search for
EncryptionKey
. Note,TokenEncryptionKey
is likely a more intention-revealing name.The text was updated successfully, but these errors were encountered: