action #6096
closed
Restrict workers to have full API access by random, individual tokens (was: change worker authentication)
Added by lnussel over 9 years ago.
Updated over 4 years ago.
Category:
Feature requests
Description
workers currently use user tokens and therefore have access to the full API. Workers should have differnt privileges that only allows them to grab jobs, set jobs to finish etc. That makes sure test code run by a worker cannot accidentally nor intentionally mess with the API.
And as dicussed in the hall earlier: every worker should have its own random token - and we should IMO offer an option to allow every worker to generate that token himself, i.e. plug&play.
coolo wrote:
And as dicussed in the hall earlier: every worker should have its own random token - and we should IMO offer an option to allow every worker to generate that token himself, i.e. plug&play.
Yes. As long as we rely on nfs anyways I think the idea with dropping a token to the shared space would be ok for now too.
- Related to action #6602: move worker credentials to workers.ini added
- Target version set to future
- Target version changed from future to future
- Category changed from 132 to Feature requests
- Status changed from New to Rejected
- Assignee set to okurz
I think by now the design has changed enough to make this whole thing obsolete, e.g. we do not rely on NFS anymore.
- Status changed from Rejected to New
- Assignee deleted (
okurz)
this has nothing to do with nfs
- Subject changed from change worker authentication to Restrict workers to have full API access by random, individual tokens (was: change worker authentication)
Changed the subject to reflect what I think you might want
- Priority changed from Normal to Low
- Status changed from New to Rejected
- Assignee set to okurz
Also available in: Atom
PDF