api functions protected by key, to control node #134

Activity

1. thepiwo

   changed the title [-]internal api functions protected by key (from env) to control node[/-] [+]api functions protected by key, to control node[/+] on Nov 20, 2017
2. cytadela8 commented on Nov 22, 2017

   

   cytadela8

   on Nov 22, 2017

   Last edited by cytadela8

   Contributor

   More actions

   I think the private API should also have a separate server so it can be only accessible from localhost.
3. thepiwo commented on Nov 22, 2017

   

   thepiwo

   on Nov 22, 2017

   ContributorAuthor

   More actions

   no, we want it to be accessible from remote as well, if the node provider wants to control a node running on a server. I think authorization token header is sufficient for security
4. d-velev

   added a commit that references this issue on Dec 11, 2017

   [GH-#134] Miner controller added, requires an uuid request header tha…

   ...

   3c69862
5. d-velev

   self-assigned this

   on Dec 11, 2017
6. thepiwo

   added 2 commits that reference this issue on Dec 12, 2017

   [GH-#134] refactor authorization check to be in router

   27f885e

   [GH-#134] moved authorization generation to server and don't override it

   220de92
7. d-velev

   added 3 commits that reference this issue on Dec 15, 2017

   [GH-#134] Removed comments in dev.exs

   919ce69

   Merge branch 'master' into GH-134

   651c044

   [GH-#134] Fixed mix.exs

   e70c134
8. thepiwo

   closed this as completedin #163on Dec 15, 2017
9. thepiwo

   added a commit that references this issue on Dec 15, 2017

   Merge pull request #163 from aeternity/GH-134

   ...

   e15b548