It may be that Galaxy is looking for a different remote user header than
your proxy is setting. I believe by default we look for HTTP_REMOTE_USER,
but this is configurable in galaxy.ini (so, you could set yours to
HTTP_USER there). Let me know if this doesn't sort it out for you and we
can dig deeper!
On Mon, Aug 31, 2015 at 3:42 PM, Ryan G <ngsbioinformat...@gmail.com> wrote:
> Hi all - I'm trying to use external user authentication with Galaxy. The
> external authentication passes to Galaxy the username with the mail domain
> at HTTP_USER.
> In galaxy.ini, I enable:
> use_remote_user = True
> When I try to access Galaxy, I get the message:
> Galaxy is configured to authenticate users via an external method (such as
> HTTP authentication in Apache), but a username was not provided by the
> upstream (proxy) server. This is generally due to a misconfiguration in the
> upstream server.
> But nothing in paster.log indicating what the error is.
> How do I track this down?
> 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:
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: