-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi John,

Seems like odd behaviour, but if that's how it works, then that'll
adequately fix my problem.

Thanks John/Iyad!

Cheers,
Eric

On 06/12/2014 09:40 AM, John Chilton wrote:
> Hey Eric,
> 
>   I am pretty sure Iyad's configuration is right - here is a similar
> config for nginx with some discussion of the API problem
> http://production-galaxy-instances-with-cloudman-and-cloudbiolinux.readthedocs.org/en/latest/#external-authentication-ldap.
> It is fine if it is "empty" it just has to be set and in fact it
> should use the real remote user if available so the UI elements that
> target the API without a key continue to function properly (which I
> guess is slowly becoming all of the UI). This is what that apache
> config and my nginx config do I believe.
> 
>   Does this answer your question, do you have lingering concerns?
> 
> -John
> 
> 
> On Thu, Jun 12, 2014 at 9:24 AM, Eric Rasche <rasche.e...@yandex.ru> wrote:
> Hi Iyad,
> 
> Thanks for posting configs! I'm very curious how this actually works for
> you.
> 
> I'm running the API scripts from the galaxy server itself, and I made
> requests to http://fqdn/galaxy/, http://localhost:####/, and
> http://localhost:####/galaxy/
> 
> The request to the fqdn unsurprisingly fails as apache answers it, and
> apache requires authentication. Both of the localhost requests also fail
> (403), indicating that galaxy was forbidding me due to lack of a
> REMOTE_USER variable being set:
> 
>>>> 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.
> 
> 
> - From my tests, I conclude that the routes under /api/ also have the
> requirement on REMOTE_USER being set. (Maybe a dev can chime in on
> this?) I'm fairly certain the only way to get the /api/ route to work
> with the apache config presented is to statically set REMOTE_USER, such
> that it's always a valid galaxy user. You don't set a static REMOTE_USER
> variable in your apache config, so when galaxy is serving requests from
> outside users, in my understanding, the REMOTE_USER var will be unset,
> and galaxy should refuse to answer it.
> 
> Cheers,
> Eric
> 
> 
> On 06/12/2014 08:31 AM, Kandalaft, Iyad wrote:
>>>> Hi Eric,
>>>>
>>>> It's not broken per se but the documentation is lacking on this front.  
>>>> You need to route your /galaxy/api folder to a proxy that does not require 
>>>> authentication.  Maybe this isn't the best way but it works for AAFC's 
>>>> production galaxy.  See my apache configuration file below:
>>>>
>>>> --------------------------------------------------------------------------------------
>>>> # Function for LowerCase conversion used in rewriterule directive
>>>> RewriteMap lc int:tolower
>>>>
>>>> # Setup the load balancer and force LDAP authentication with group file 
>>>> authorization
>>>> <Proxy balancer://galaxy-prod/*>
>>>>         BalancerMember http://localhost:60000
>>>>         BalancerMember http://localhost:60001
>>>>         BalancerMember http://localhost:60002
>>>>
>>>>         # LDAP based authentication
>>>>         AuthName "Galaxy - Login with AAFC credentials"
>>>>         AuthType Basic
>>>>         AuthBasicAuthoritative off
>>>>         AuthBasicProvider ldap
>>>>
>>>>         AuthLDAPURL "REDACTED"
>>>>         AuthLDAPBindDN 'REDACTED'
>>>>         AuthLDAPBindPassword "REDACTED"
>>>>
>>>>         # File based authorization
>>>>         AuthGroupFile /home/galaxy/permitted_users
>>>>         Require group galaxy-users
>>>>
>>>>         RewriteEngine on
>>>>
>>>>         # Convert the sAMAccountName to lower case
>>>>         RewriteRule ^ - 
>>>> [E=AUTHENTICATE_sAMAccountName:${lc:%{ENV:AUTHENTICATE_sAMAccountName}}]
>>>>
>>>>         # Set the REMOTE_USER header to the contents of the LDAP query 
>>>> response's "sAMAccountName" attribute
>>>>         RequestHeader set REMOTE_USER %{AUTHENTICATE_sAMAccountName}e
>>>> </Proxy>
>>>>
>>>> <Proxy balancer://galaxy-prod-noauth/*>
>>>>         BalancerMember http://localhost:60000
>>>>         BalancerMember http://localhost:60001
>>>>         BalancerMember http://localhost:60002
>>>>
>>>>         # Required to allow unauthenticated access
>>>>         # Not clear why this is so
>>>>         Satisfy any
>>>> </Proxy>
>>>>
>>>> # Bypass authentication for the api endpoints when a "key" get variable is 
>>>> provided by proxying directly to the galaxy web server
>>>> RewriteCond %{QUERY_STRING} key=
>>>> RewriteRule ^/galaxy/api/(.*) balancer://galaxy-prod-noauth/api/$1 [P]
>>>>
>>>> # Bypass authentication for display servers
>>>> RewriteCond HTTP_HOST =hgw1.cse.ucsc.edu [OR,NC]
>>>> RewriteCond HTTP_HOST =hgw2.cse.ucsc.edu [OR,NC]
>>>> RewriteCond HTTP_HOST =hgw3.cse.ucsc.edu [OR,NC]
>>>> RewriteCond HTTP_HOST =hgw4.cse.ucsc.edu [OR,NC]
>>>> RewriteCond HTTP_HOST =hgw5.cse.ucsc.edu [OR,NC]
>>>> RewriteCond HTTP_HOST =hgw7.cse.ucsc.edu [OR,NC]
>>>> RewriteCond HTTP_HOST =hgw8.cse.ucsc.edu [NC]
>>>> RewriteRule ^/galaxy/root/display_as(.*) 
>>>> balancer://galaxy-prod-noauth/root/display_as$1 [P]
>>>>
>>>> # Serve static content directly from apache
>>>> RewriteRule ^/galaxy/static/style/(.*) 
>>>> /home/galaxy/galaxy-dist/static/june_2007_style/blue/$1 [L]
>>>> RewriteRule ^/galaxy/static/scripts/(.*) 
>>>> /home/galaxy/galaxy-dist/static/scripts/packed/$1 [L]
>>>> RewriteRule ^/galaxy/static/(.*) /home/galaxy/galaxy-dist/static/$1 [L]
>>>> RewriteRule ^/galaxy/favicon.ico 
>>>> /home/galaxy/galaxy-dist/static/favicon.ico [L]
>>>> RewriteRule ^/galaxy/robots.txt /home/galaxy/galaxy-dist/static/robots.txt 
>>>> [L]
>>>>
>>>> # Route all other traffic through the load balancer
>>>> RewriteRule ^/galaxy/(.*)$ balancer://galaxy-prod/$1 [P]
>>>> ------------------------------------------------------------------------------
>>>>
>>>>
>>>>
>>>> Regards,
>>>>
>>>> Iyad Kandalaft
>>>> Microbial Biodiversity Bioinformatics
>>>> Agriculture and Agri-Food Canada | Agriculture et Agroalimentaire Canada
>>>> 960 Carling Ave.| 960 Ave. Carling
>>>> Ottawa, ON| Ottawa (ON) K1A 0C6
>>>> E-mail Address / Adresse courriel  iyad.kandal...@agr.gc.ca
>>>> Telephone | Téléphone 613-759-1228
>>>> Facsimile | Télécopieur 613-759-1701
>>>> Teletypewriter | Téléimprimeur 613-773-2600
>>>> Government of Canada | Gouvernement du Canada
>>>>
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: galaxy-dev-boun...@lists.bx.psu.edu 
>>>> [mailto:galaxy-dev-boun...@lists.bx.psu.edu] On Behalf Of Eric Rasche
>>>> Sent: Wednesday, June 11, 2014 8:43 PM
>>>> To: galaxy-dev@lists.bx.psu.edu
>>>> Subject: [galaxy-dev] bug: API broken under remote_user
>>>>
>>>> https://trello.com/c/AGKePuHZ/1630-expose-use-remote-user-via-configuration-api
>>>>
>>>> I don't know if this is the correct card (it's been a long day and I may 
>>>> be misreading it) but the API is completely broken under REMOTE_USER 
>>>> authentication.
>>>>
>>>> running ./scripts/api/display.py {key} http://localhost:8300 returns 403 
>>>> forbidden.
>>>>
>>>> running ./scripts/api/display.py {key} https://fqdn/galaxy/ returns 401 
>>>> Authorization Required
>>>>
>>>> ___________________________________________________________
>>>> 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/
>>>>
> 
>> ___________________________________________________________
>> 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/

- -- 
Эрик Раше
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)

iQIcBAEBAgAGBQJTmb62AAoJEMqDXdrsMcpVupMQAK5ELIUQJ6wuBxxYYiRJpsXp
ifKAKkdsxz0VhYP1c5vHpihkNErxrOetgtyqc5OvnsTYtIl3aRqUWkfB+VLvEAcH
tPnGOl5tGxT6J213SK54U1qX4gPNooXBCt4w7Q09unqgOn4T1ROmTb6Vnfgfv05E
f4hMj7l7xtKoKfF8GopYr3EEY6m/EVqNB91rlOCyNdwizi69ovPatJn2MJlGxTov
2S11k2trNmZOdY+mcLW6n4UwNr64IOYmq+tOxGUw5iOmQUfPTMPNDeiCPxE8MBrX
tlPgndubxc+fLV6bIeWUkfUW6kdOZD71QmNlJzlfA30+Az2xR/p1ThK0ES8Rvc73
coQUjOLokY5b4DczM1ZcnYeayAJCWgFINtTRTJmLVXw4e1h4jzmuVddwNQkj2EDL
jcIMq5keF6ngV6v2EPrK2C8kbXHxpHoGmglFZOIXgbh5mmWjxyViaOKum/V97Zbf
/tMfajOc0rDUd23qYiYyG8lhlz6kYtRbgnAq6gyaGe2kX+rDEx3UMp/GMqTzvdxE
PzNYlPpXRqqId5bo1KaiaWCMGp8Bru4nAKL+7Qtjqdy6bUzCfoQ8zLJ4hxP6lXK9
zRoCFh2h5BCjTB7DJ+B6p/I01/ceKTKA7haW/Kkba75Wej9dRuUYF3mMyAYndUzq
c5gMQGTEpFFoaqUJrzlY
=i0j3
-----END PGP SIGNATURE-----
___________________________________________________________
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/

Reply via email to