Description of problem: I cannot login with username + password after the upgrade to Version 0.16.0 Version-Release number of selected component (if applicable): rpm -qf `which bkr` beaker-client-0.16.0-2.el6eng.noarch How reproducible: always Steps to Reproduce: 1. [psklenar@liver2 ~]$ bkr whoami XML-RPC fault: <class 'bkr.server.identity.IdentityFailure'>: Anonymous access denied [psklenar@liver2 ~]$ cat ~/.beaker_client/config HUB_URL = "https://beaker.engineering.redhat.com" AUTH_METHOD = "password" USERNAME = "tip" PASSWORD = "XXXXXXXXXXXXXX" [psklenar@liver2 ~]$ rpm -qf `which bkr` beaker-client-0.16.0-2.el6eng.noarch [psklenar@liver2 ~]$ bkr whoami XML-RPC fault: <type 'exceptions.ValueError'>:expected pbkdf2_sha512 hash, got pbkdf2_sha512 config string instead [psklenar@liver2 ~]$ bkr whoami XML-RPC fault: <type 'exceptions.ValueError'>:expected pbkdf2_sha512 hash, got pbkdf2_sha512 config string instead Actual results: pbkdf2_sha512 hash, got pbkdf2_sha512 config string instead Expected results: it works Additional info:
I was able to reproduce this as well using the bkr client set to password auth. I also run into this issue when logging into the web ui using password auth (reproducible by disabling kerberos auth in my browser).
This is not a bug, but rather a minor mishap during the Beaker 0.16 upgrade of our internal instance affecting two bot accounts: cloudqe and tip. I already commented on the RT ticket but I'll repeat it here. Part of the upgrade was to extend the password column from 40 characters to TEXT, to handle the longer password hashes. The Beaker application was accidentally started before the database upgrades were complete, and the two affected bot accounts logged in during this time, so Beaker stored the new password hash and MySQL silently truncated it to 40 characters. The solution is to reset the password for the two affected accounts.
(In reply to J.C. Molet from comment #4) > I was able to reproduce this as well using the bkr client set to password > auth. I also run into this issue when logging into the web ui using > password auth (reproducible by disabling kerberos auth in my browser). The web UI for Red Hat's Beaker instance only accepts Kerberos authentication, it doesn't use Beaker passwords. If you are having trouble with Kerberos authentication then it is a different issue than the one in this bug.
HI, there is still the same issue: [psklenar@liver2 ~]$ bkr whoami XML-RPC fault: <type 'exceptions.ValueError'>:expected pbkdf2_sha512 hash, got pbkdf2_sha512 config string instead [psklenar@liver2 ~]$ bkr task-details /distribution/reservesys XML-RPC fault: <type 'exceptions.ValueError'>:expected pbkdf2_sha512 hash, got pbkdf2_sha512 config string instead [psklenar@liver2 ~]$ date Fri Mar 21 08:47:25 CET 2014
Note that the upstream Beaker project cannot help with instance specific account issues, such as those impacting accounts that had their password data corrupted by attempting to log in while the database upgrade was still in progress.