I solved this by manually editing the user's emails in the database. I did
this during the downtime, and just switched their old email address to
their LDAP address, causing them to see their "old" histories, and no new
accounts were generated.
If your users have already logged in (and thus have two accounts, one old,
one new) it's slightly more complicated.
Your best bet is to set up some downtime immediately, and do the above,
causing the users to lose anything in their "new" accounts.
Failing that, a method of last resort:
You can update history IDs to the new users, i.e. find a mapping from old
email + old user ID to new email + new user ID, and then run queries
history set user_id=new_user_id where user_id=old_user_id but that only
migrates histories, I don't know what else is keyed on user IDs (probably
data libraries? Workflows? Hmm.)
Hope that helps,
2015-04-30 1:01 GMT-05:00 Teshome Dagne Mulugeta <teshome.mulug...@nmbu.no>:
> We are currently using galaxy specific login using email address. We
> changed the authentication to LDAP. Most users email address doesn't match
> with their registered email address in LDAP. Now, users are not able to see
> their previous works which is expected of course but I have no clue how to
> fix it. Please help.
> Please keep all replies on the list by using "reply all"
> in your mail client. To manage your subscriptions to this
> and other Galaxy lists, please use the interface at:
> To search Galaxy mailing lists use the unified search at:
Center for Phage Technology
Rm 312A, BioBio
Texas A&M University
College Station, TX 77843
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
To search Galaxy mailing lists use the unified search at: