{"action":"created","issue":{"url":"https://api.github.com/repos/Mashape/kong/issues/1237","repository_url":"https://api.github.com/repos/Mashape/kong","labels_url":"https://api.github.com/repos/Mashape/kong/issues/1237/labels{/name}","comments_url":"https://api.github.com/repos/Mashape/kong/issues/1237/comments","events_url":"https://api.github.com/repos/Mashape/kong/issues/1237/events","html_url":"https://github.com/Mashape/kong/issues/1237","id":155958997,"number":1237,"title":"Storing sensitive information in database","user":{"login":"mleace","id":8587856,"avatar_url":"https://avatars.githubusercontent.com/u/8587856?v=3","gravatar_id":"","url":"https://api.github.com/users/mleace","html_url":"https://github.com/mleace","followers_url":"https://api.github.com/users/mleace/followers","following_url":"https://api.github.com/users/mleace/following{/other_user}","gists_url":"https://api.github.com/users/mleace/gists{/gist_id}","starred_url":"https://api.github.com/users/mleace/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mleace/subscriptions","organizations_url":"https://api.github.com/users/mleace/orgs","repos_url":"https://api.github.com/users/mleace/repos","events_url":"https://api.github.com/users/mleace/events{/privacy}","received_events_url":"https://api.github.com/users/mleace/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/Mashape/kong/labels/area/admin%20api","name":"area/admin api","color":"d4c5f9"},{"url":"https://api.github.com/repos/Mashape/kong/labels/task/proposal","name":"task/proposal","color":"bfe5bf"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":19,"created_at":"2016-05-20T13:07:12Z","updated_at":"2016-08-01T17:57:18Z","closed_at":null,"body":"Hello,\r\n\r\nas far as I know, sensitive informations (like API keys, OAuth client secrets, OAuth access & refresh tokens etc.) are stored in database in plain text, which might be a security issue. Is there any way to store these informations encrypted (or hashed when applicable). If not, is there a plan to implement such feature? I know there will be a performance penalty, but still this might be necessary in some environments.\r\n\r\nThank you!"},"comment":{"url":"https://api.github.com/repos/Mashape/kong/issues/comments/236656711","html_url":"https://github.com/Mashape/kong/issues/1237#issuecomment-236656711","issue_url":"https://api.github.com/repos/Mashape/kong/issues/1237","id":236656711,"user":{"login":"djMax","id":240684,"avatar_url":"https://avatars.githubusercontent.com/u/240684?v=3","gravatar_id":"","url":"https://api.github.com/users/djMax","html_url":"https://github.com/djMax","followers_url":"https://api.github.com/users/djMax/followers","following_url":"https://api.github.com/users/djMax/following{/other_user}","gists_url":"https://api.github.com/users/djMax/gists{/gist_id}","starred_url":"https://api.github.com/users/djMax/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/djMax/subscriptions","organizations_url":"https://api.github.com/users/djMax/orgs","repos_url":"https://api.github.com/users/djMax/repos","events_url":"https://api.github.com/users/djMax/events{/privacy}","received_events_url":"https://api.github.com/users/djMax/received_events","type":"User","site_admin":false},"created_at":"2016-08-01T17:57:18Z","updated_at":"2016-08-01T17:57:18Z","body":"I've got a fork that fixes this for provision_key which for us is probably the worst offender. For refresh_token I assume this is much harder because of the lookup?"}}
{"actor":{"display_login":"djMax"}}