Ok I got it.  I had to update the email address field to match what the REMOTE_USER variable was being set my Apache.

On Wed, Sep 7, 2016 at 1:41 PM, Ryan G <ngsbioinformatics@gmail.com> wrote:
Sorry, missed your other questions...

external authentication via apache...yes.  Its working well for us.
The userid is the same.  I'm clearly missing something.   I need to find in the code where this is and add some debugging statements.

On Wed, Sep 7, 2016 at 12:15 PM, Hans-Rudolf Hotz <hrh@fmi.ch> wrote:
Hi Ryan

Are you doing external authentication via apache?

if so, I suggest to change the value in the 'external' column from 'f' to 't' in the galaxy_user table.

also, check, whether the e-mail used is really the same as the one coming from your external authentication system.

However, be very careful, whenever you manually interact with the Galaxy PostgreSQL database. Make sure you have an up-to-date back-up.

Hope this helps,

On 09/07/2016 05:27 PM, Ryan G wrote:
Hi all - I'm having a problem with a user account and Galaxy getting
confused with it being internal vs external.

When we first set up galaxy, we were using Galaxy's internal
authentication system.  This worked well but all our users then had
another password to keep track of.

We activated external user authentication a few months ago and it works
fine for us.

This user hasn't logged in since and recently tried but is unable to.

I discovered her account in Galaxy appears as an internal account eg
created before we were using external authentication.   Now that we have
external authentication, Galaxy doesn't recognize her and she gets the
user_disabled page whenever she tries to log in.

Is there a way I can change her account in Galaxy from being an internal
to an external account?


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: