https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842015-01-28T11:48:12ZopenSUSE Project Management ToolopenQA Project - action #6096: Restrict workers to have full API access by random, individual tokens (was: change worker authentication)https://progress.opensuse.org/issues/6096?journal_id=147102015-01-28T11:48:12Zcoolocoolo@suse.com
<ul></ul><p>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.</p>
openQA Project - action #6096: Restrict workers to have full API access by random, individual tokens (was: change worker authentication)https://progress.opensuse.org/issues/6096?journal_id=147122015-01-28T14:56:56Zlnussellnussel@suse.com
<ul></ul><p>coolo wrote:</p>
<blockquote>
<p>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.</p>
</blockquote>
<p>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.</p>
openQA Project - action #6096: Restrict workers to have full API access by random, individual tokens (was: change worker authentication)https://progress.opensuse.org/issues/6096?journal_id=152762015-03-10T08:19:57Zlnussellnussel@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-6 priority-4 priority-default closed" href="/issues/6602">action #6602</a>: move worker credentials to workers.ini</i> added</li></ul> openQA Project - action #6096: Restrict workers to have full API access by random, individual tokens (was: change worker authentication)https://progress.opensuse.org/issues/6096?journal_id=200422016-01-11T09:15:28Zokurzokurz@suse.com
<ul><li><strong>Category</strong> set to <i>132</i></li></ul> openQA Project - action #6096: Restrict workers to have full API access by random, individual tokens (was: change worker authentication)https://progress.opensuse.org/issues/6096?journal_id=327782016-11-27T15:23:08Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> set to <i>future</i></li></ul> openQA Project - action #6096: Restrict workers to have full API access by random, individual tokens (was: change worker authentication)https://progress.opensuse.org/issues/6096?journal_id=1296252018-06-15T19:07:25Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> changed from <i>future</i> to <i>future</i></li></ul> openQA Project - action #6096: Restrict workers to have full API access by random, individual tokens (was: change worker authentication)https://progress.opensuse.org/issues/6096?journal_id=2222542019-06-20T15:29:49Zokurzokurz@suse.com
<ul><li><strong>Category</strong> changed from <i>132</i> to <i>Feature requests</i></li></ul> openQA Project - action #6096: Restrict workers to have full API access by random, individual tokens (was: change worker authentication)https://progress.opensuse.org/issues/6096?journal_id=2418892019-09-07T21:53:50Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Rejected</i></li><li><strong>Assignee</strong> set to <i>okurz</i></li></ul><p>I think by now the design has changed enough to make this whole thing obsolete, e.g. we do not rely on NFS anymore.</p>
openQA Project - action #6096: Restrict workers to have full API access by random, individual tokens (was: change worker authentication)https://progress.opensuse.org/issues/6096?journal_id=2419282019-09-08T18:30:24Zcoolocoolo@suse.com
<ul><li><strong>Status</strong> changed from <i>Rejected</i> to <i>New</i></li><li><strong>Assignee</strong> deleted (<del><i>okurz</i></del>)</li></ul><p>this has nothing to do with nfs</p>
openQA Project - action #6096: Restrict workers to have full API access by random, individual tokens (was: change worker authentication)https://progress.opensuse.org/issues/6096?journal_id=2419402019-09-08T20:07:19Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>change worker authentication</i> to <i>Restrict workers to have full API access by random, individual tokens (was: change worker authentication)</i></li></ul><p>Changed the subject to reflect what I think you might want</p>
openQA Project - action #6096: Restrict workers to have full API access by random, individual tokens (was: change worker authentication)https://progress.opensuse.org/issues/6096?journal_id=2639272019-12-11T14:50:34Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-6 status-3 priority-4 priority-default closed parent" href="/issues/6558">coordination #6558</a>: [epic] add/edit/remove users</i> added</li></ul> openQA Project - action #6096: Restrict workers to have full API access by random, individual tokens (was: change worker authentication)https://progress.opensuse.org/issues/6096?journal_id=2898872020-04-01T11:49:20Zokurzokurz@suse.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li></ul> openQA Project - action #6096: Restrict workers to have full API access by random, individual tokens (was: change worker authentication)https://progress.opensuse.org/issues/6096?journal_id=2952762020-04-22T21:31:38Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Rejected</i></li><li><strong>Assignee</strong> set to <i>okurz</i></li></ul><p>-> <a class="issue tracker-6 status-1 priority-3 priority-lowest" title="coordination: [epic] Various feature requests (New)" href="https://progress.opensuse.org/issues/65271">#65271</a></p>