I can't confirm it is going to work without negative repercussions - I
can only say that I cannot think of any non-obvious problems that
would result from doing this. It seems like it is going to be the
right thing to do in your case (but no promises :)).
If it works, it would be super awesome if you update the wiki - thanks
for taking the time to do that!
On Mon, Jul 25, 2016 at 9:00 AM, Hans-Rudolf Hotz <hrh(a)fmi.ch> wrote:
Our production server uses Apache to handle external user authentication.
I have now set up a new test server (16.04) which handles external user
authentication via LDAP using the auth_conf file. This works nicely when
using an empty database (I have managed to solve all last weeks problems).
I have now connected my test server to a copy of the PostgreSQL database
used on our production server. I try to log in, and I get:
"This account was created for use with an external authentication method,
and the login fails.
If I now set external = 'f' in the galaxy_user table, it works
Since manually modifying the database is a bad thing, I just want to double
check, whether this is the right way to do it?
If so, I will add a line or two to the wiki
Many thanks for your help
Hans-Rudolf Hotz, PhD
Friedrich Miescher Institute for Biomedical Research
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: