Hi,
> ...so it appears that the authentication succeeded and is being relayed
> to Gerrit (along with the password which should be irrelevant). However,
> Gerrit is seemingly ignoring the username, unless I need to do something
> with Settings after I am seen as Anonymous Coward, to convince it who I
> really am. In this case "DaveMaul" is already known to Gerrit as a user
> (left over from our initial configuration which was using
> http.auth=DEVELOPMENT_BECOME_ANY_ACCOUNT)
I also had this problem recently. The root cause is that your DaveMaul
user created while DEVELOPMENT_BECOME_ANY_ACCOUNT was active does not
have an external_id of "gerrit:DaveMaul" in the account_external_ids
database table.
Apparently, Gerrit tries to match your Authorization header of
"DaveMaul" against an existing user, doesn't find any, and then decides
to create a new use named "DaveMaul" -- which also fails.
If you have gsql access, you can just do the following:
ssh -p 29418 USERNAME@HOST gerrit gsql
On the GSQL prompt:
SELECT * FROM account_external_ids;
Note the account_id of the existing DaveMail, update and verify:
INSERT INTO account_external_ids VALUES(ACCOUNT_ID, NULL, NULL,
'gerrit:DaveMaul');
SELECT * FROM account_external_ids;
\q
Hope this helps,
Andreas
--
Codetrails GmbH
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Phone:
+49-6151-276-7092
Mobile:
+49-170-811-3791
http://www.codetrails.com/
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940