René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Allow processor to have their own API key","articleBody":"**Is your feature request related to a problem? Please describe.**\r\nProcessor can't login on their own, they have to use the JWT from management.\r\n\r\n**Describe the solution you'd like**\r\n- Add `apiKey` to processor table.\r\n- When the manager add a new processor, it should return the processor informations including the `apiKey` generated.\r\n- Add a way to regenerate the `apiKey` from the manager only (for invalidation or if the apiKey was leaked).\r\n\r\n**Describe alternatives you've considered**\r\nNone.\r\n\r\n**Additional context**\r\n- The `apiKey` should only give access to the processor endpoints and nothing else.\r\n- The `apiKey` should be random and secure enough. Since we are using JWT for manager and subject token, we should use the same.\r\n- Blocked by #384 \r\n","author":{"url":"https://github.com/Nelrohd","@type":"Person","name":"Nelrohd"},"datePublished":"2018-08-29T06:46:56.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/433/ClearGDPR/issues/433"}