Re: [galaxy-dev] external authentication - empty REMOTE_USER

Hi, thanks for the quick reply ! I did edit the remoteuser.py file and started the daemon again, but there's no change in the output in paster.log. Am I missing something ? F.T 2015-10-21 12:11 GMT+02:00 Floreline TOUCHARD : > Hi, > > I've got an issue with my

Re: [galaxy-dev] external authentication - empty REMOTE_USER

Hi, here is some additional information : - I have no change in my paster.log with my current galaxy.conf file. - If I force the connexion with a user (with a RequestHeader set REMOTE_USER "" in galaxy.conf), it works. My galaxy instance open on my user session, and I get a

[galaxy-dev] using Bioblend with external authentication

Hi We would like to start using BioBlend on our production servers (which use external authentication) as well. We have changed the apache conf file by adding Satisfy Any Allow from all Nevertheless, we still get the following error, when using one of the

Re: [galaxy-dev] using Bioblend with external authentication

My guess is that it has to do with the prefix there. Is the Galaxy API at galaxy-dev.fmi.ch/galaxy/api or galaxy-dev.fmi.ch/api? On Thu, Oct 22, 2015 at 6:41 AM Hans-Rudolf Hotz wrote: > Hi > > We would like to start using BioBlend on our production servers (which > use external

[galaxy-dev] Deleting / deprecating an empty Tool Shed repository?

Hi all, Following the Biopython 1.66 release, I will be creating: https://testtoolshed.g2.bx.psu.edu/view/biopython/package_biopython_1_66/ https://toolshed.g2.bx.psu.edu/view/biopython/package_biopython_1_66/ Due to user error and a planemo bug [1], I accidentally created the following on the