Bug 843687
Summary: | authenticate calls from lab machines to beaker-proxy with a signed token unique per recipe | ||
---|---|---|---|
Product: | [Retired] Beaker | Reporter: | Dan Callaghan <dcallagh> |
Component: | lab controller | Assignee: | beaker-dev-list |
Status: | CLOSED WONTFIX | QA Contact: | tools-bugs <tools-bugs> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 0.9 | CC: | bpeck, cbouchar, stl, tools-bugs, xtian |
Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | Misc | ||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | 572834 | Environment: | |
Last Closed: | 2020-11-19 22:08:53 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1215894 |
Description
Dan Callaghan
2012-07-27 04:01:23 UTC
"signed-token-based authentication" seems to (vaguely) resemble idea sketched at [bug 1169007 comment 0]: > Restriction on "only fellow nodes in the same task can be fenced" > could be for the sake of simplicity implemented by common knowledge > of some hash (key) that would have to be included in the actual > fencing request. + adding "such hash could be exported automatically as an env. variable to the machines involved in the particular job" I was considering a scenario of turning unrelated machine of *by accident*, which I would really prefer to be prevented rather than having to explain someone else that, e.g., cluster configuration conversion utility had a bug in it :) |