action #6096
closedRestrict workers to have full API access by random, individual tokens (was: change worker authentication)
0%
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.
Updated by coolo over 9 years ago
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.
Updated by lnussel over 9 years ago
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.
Updated by lnussel over 9 years ago
- Related to action #6602: move worker credentials to workers.ini added
Updated by okurz about 5 years ago
- 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.
Updated by coolo about 5 years ago
- Status changed from Rejected to New
- Assignee deleted (
okurz)
this has nothing to do with nfs
Updated by okurz about 5 years ago
- 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
Updated by okurz almost 5 years ago
- Related to coordination #6558: [epic] add/edit/remove users added
Updated by okurz over 4 years ago
- Status changed from New to Rejected
- Assignee set to okurz
-> #65271