Installing Galaxy behind an Apache proxy using mod_auth_cas for user auth
Dear all, I would like to set up a local Galaxy instance behind an Apache server with our local CAS for authentication. It would be great if you could give me a hint for the httpd.conf. I have the problem that after authenticating against CAS in the browser, I get following error message and REMOTE_USER doesn't seem to be in the HTTP header for Galaxy (I can see the REMOTE_USER in the access_log of Apache but not any more in paster.log of Galaxy). "Access to Galaxy is denied 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." I know that the same question was already asked in the following post but I haven't seen an option to extend the post and I haven't found an answer. http://dev.list.galaxyproject.org/Installing-Galaxy-behind-an-Apache-proxy-u... Any help is much appreciated. Many thanks, Sandra
Dear all, I have found a solution but I can unfortunately not explain why your solution on the Admin pages is not working. The following entries in httpd.conf solved the problem in our environment. Maybe this is useful for other CAS users. Best, Sandra RewriteEngine on <Location "/"> # Define the authentication method AuthType CAS AuthName Galaxy Require valid-user </Location> # Proxy Configurations ProxyVia On ProxyPassInterpolateEnv On <Proxy *> Order allow,deny Allow from all </Proxy> ProxyPass / http://galaxy.crc.nd.edu:8080/ ProxyPassReverse / http://galaxy.crc.nd.edu:8080/ RequestHeader set REMOTE_USER %{REMOTE_USER}s SSLProxyEngine On AllowCONNECT 8080 RewriteRule ^(.*) http://galaxy.crc.nd.edu:8080$1 [P] ________________________________________ From: galaxy-dev-bounces@lists.bx.psu.edu [galaxy-dev-bounces@lists.bx.psu.edu] On Behalf Of Sandra Gesing [sandra.gesing@nd.edu] Sent: Tuesday, November 05, 2013 5:46 PM To: galaxy-dev@lists.bx.psu.edu Subject: [galaxy-dev] Installing Galaxy behind an Apache proxy using mod_auth_cas for user auth Dear all, I would like to set up a local Galaxy instance behind an Apache server with our local CAS for authentication. It would be great if you could give me a hint for the httpd.conf. I have the problem that after authenticating against CAS in the browser, I get following error message and REMOTE_USER doesn't seem to be in the HTTP header for Galaxy (I can see the REMOTE_USER in the access_log of Apache but not any more in paster.log of Galaxy). "Access to Galaxy is denied 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." I know that the same question was already asked in the following post but I haven't seen an option to extend the post and I haven't found an answer. http://dev.list.galaxyproject.org/Installing-Galaxy-behind-an-Apache-proxy-u... Any help is much appreciated. Many thanks, Sandra ___________________________________________________________ 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: http://lists.bx.psu.edu/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
participants (1)
-
Sandra Gesing