{"action":"created","issue":{"url":"https://api.github.com/repos/cantino/huginn/issues/76","repository_url":"https://api.github.com/repos/cantino/huginn","labels_url":"https://api.github.com/repos/cantino/huginn/issues/76/labels{/name}","comments_url":"https://api.github.com/repos/cantino/huginn/issues/76/comments","events_url":"https://api.github.com/repos/cantino/huginn/issues/76/events","html_url":"https://github.com/cantino/huginn/issues/76","id":17026959,"number":76,"title":"API key management","user":{"login":"crawfordcomeaux","id":921386,"avatar_url":"https://avatars.githubusercontent.com/u/921386?v=3","gravatar_id":"","url":"https://api.github.com/users/crawfordcomeaux","html_url":"https://github.com/crawfordcomeaux","followers_url":"https://api.github.com/users/crawfordcomeaux/followers","following_url":"https://api.github.com/users/crawfordcomeaux/following{/other_user}","gists_url":"https://api.github.com/users/crawfordcomeaux/gists{/gist_id}","starred_url":"https://api.github.com/users/crawfordcomeaux/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/crawfordcomeaux/subscriptions","organizations_url":"https://api.github.com/users/crawfordcomeaux/orgs","repos_url":"https://api.github.com/users/crawfordcomeaux/repos","events_url":"https://api.github.com/users/crawfordcomeaux/events{/privacy}","received_events_url":"https://api.github.com/users/crawfordcomeaux/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/cantino/huginn/labels/discussion","name":"discussion","color":"fbca04"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2013-07-22T00:29:10Z","updated_at":"2016-02-14T22:15:32Z","closed_at":"2016-02-14T22:15:32Z","body":"It seems like it'd be worth discussing ways to allow for easy API key management. One thing to keep in mind is the distinction between app keys & user keys: correct me if I'm wrong, but I think a single Huginn deployment can be configured with a single Twitter consumer key & consumer secret, but oauth creds for each user. \r\n\r\nMy thoughts:\r\n\r\nQuick & dirty:  App keys go in .env, user keys get their own fields on the Account screen.\r\n\r\nBetter: Same as above, but separate API keys view and menu item to the Account dropdown.\r\n\r\nBetterer: Same as above, but user keys can be accessed/modified from agent creation page and get cached for future instances of that agent. If the user is the admin, keys for the app will be available there, too."},"comment":{"url":"https://api.github.com/repos/cantino/huginn/issues/comments/183991227","html_url":"https://github.com/cantino/huginn/issues/76#issuecomment-183991227","issue_url":"https://api.github.com/repos/cantino/huginn/issues/76","id":183991227,"user":{"login":"cantino","id":83835,"avatar_url":"https://avatars.githubusercontent.com/u/83835?v=3","gravatar_id":"","url":"https://api.github.com/users/cantino","html_url":"https://github.com/cantino","followers_url":"https://api.github.com/users/cantino/followers","following_url":"https://api.github.com/users/cantino/following{/other_user}","gists_url":"https://api.github.com/users/cantino/gists{/gist_id}","starred_url":"https://api.github.com/users/cantino/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cantino/subscriptions","organizations_url":"https://api.github.com/users/cantino/orgs","repos_url":"https://api.github.com/users/cantino/repos","events_url":"https://api.github.com/users/cantino/events{/privacy}","received_events_url":"https://api.github.com/users/cantino/received_events","type":"User","site_admin":false},"created_at":"2016-02-14T22:15:32Z","updated_at":"2016-02-14T22:15:32Z","body":"Closing.  We have Credentials and are fairly 12-factor.  We could add a Liquid tag to access the ENV if needed."}}