Since 0.6 Beaker has had the "proxy user" feature whereby accounts can be granted permission to authenticate to Beaker as any other user. The purpose of this feature is for bots or scripts running as trusted service accounts (generally, under the control of the Beaker administrator only) to perform actions on behalf of real users. A service needs to pass an extra parameter to the auth.login_* XMLRPC methods: https://beaker-project.org/docs/server-api/xmlrpc.html#authentication The bkr client should also expose this functionality, so that scripts can use this feature when invoking bkr (without having to make XMLRPC calls directly).
I suggest a new common option --proxy-user=<username> which, when set, is passed as the extra param to the login methods. This option should *not* be included in --help, we don't want it to appear in the help message for every single subcommand and confuse people when regular users will never be able to use it. It should appear in bkr(1) alongside the other common auth options however.
(In reply to Dan Callaghan from comment #2) > I suggest a new common option --proxy-user=<username> which, when set, is > passed as the extra param to the login methods. Proposed patch v1: http://gerrit.beaker-project.org/#/c/4030/
*** Bug 1203041 has been marked as a duplicate of this bug. ***
Patch which was merged: http://gerrit.beaker-project.org/#/c/4035/ This fix is available for testing in the beaker client packages (beaker-client-19.4-0.git.109.fc3396d) available from https://beaker-project.org/nightlies/develop/
Beaker 20.0 has been released.