action #6096

Restrict workers to have full API access by random, individual tokens (was: change worker authentication)

Added by lnussel about 5 years ago. Updated 6 months ago.

Status:NewStart date:28/01/2015
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Feature requests
Target version:QA - future
Difficulty:
Duration:

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.


Related issues

Related to openQA Project - action #6602: move worker credentials to workers.ini Rejected 10/03/2015
Related to openQA Project - action #6558: add/edit/remove users Workable 05/03/2015

History

#1 Updated by coolo about 5 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.

#2 Updated by lnussel about 5 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.

#3 Updated by lnussel almost 5 years ago

  • Related to action #6602: move worker credentials to workers.ini added

#4 Updated by okurz about 4 years ago

  • Category set to 132

#5 Updated by okurz about 3 years ago

  • Target version set to future

#6 Updated by okurz over 1 year ago

  • Target version changed from future to future

#7 Updated by okurz 8 months ago

  • Category changed from 132 to Feature requests

#8 Updated by okurz 6 months 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.

#9 Updated by coolo 6 months ago

  • Status changed from Rejected to New
  • Assignee deleted (okurz)

this has nothing to do with nfs

#10 Updated by okurz 6 months 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

#11 Updated by okurz 2 months ago

Also available in: Atom PDF