On 01/25/2011 03:44 PM, Davide Cittaro wrote:
On Jan 25, 2011, at 3:40 PM, Hans-Rudolf Hotz wrote:
Hi Davide
We were in a similar situation when we switched to external authentication. Although, only one user was affected and we were using MySQL.
I could fix it by changing the contents of the "galaxy_user" with a few sql statements. BUT, be careful! you can do a lot of damage to the database.
Could you post the sql statement? I guess that should work in the same way! Thanks d
Have a look at the "galaxy_user" table to identify the 'broken' row, ie the wrong "e-mail".
and then you can execute:
update galaxy_user set email = "foo@fmi.ch" where email = "wrong_name@wrong_host.ch";
you might have to change the "name" in the "role" table accordingly.....
Once again be careful with what you are doing, and don't blame me if you create a mess ;)
Hans
Regards, Hans
On 01/25/2011 02:40 PM, Davide Cittaro wrote:
Dear all, Our local galaxy instance uses apache authentication to log users. This said, some users have no "User Name" and some other have a wrong "User name" (probably because they have been added before the apache integration). I just wonder if there's a way to modify the user names directly in the postgres database (I'm pretty sure that is possible...).
Thanks
d /* Davide Cittaro, PhD
Cogentech - Consortium for Genomic Technologies via adamello, 16 20139 Milano Italy
tel.: +39(02)574303007 e-mail: davide.cittaro@ifom-ieo-campus.it */
galaxy-dev mailing list galaxy-dev@lists.bx.psu.edu http://lists.bx.psu.edu/listinfo/galaxy-dev
/* Davide Cittaro, PhD
Cogentech - Consortium for Genomic Technologies via adamello, 16 20139 Milano Italy
tel.: +39(02)574303007 e-mail: davide.cittaro@ifom-ieo-campus.it */