On 28/11/12 06:12, Harris Shapiro wrote:
2) Overly aggressive “Security-Enhanced Linux” settings, which were
silently blocking some of the needed HTTP communication. I never did
find any log messages for this; I just guessed it might be an issue
and turned it off. Everything then happily
Hi Harris,
I can't pin-point your issue exactly, to be honest I don't quite
remember how I got to this working configuration. Still please take a
look at this configuration as I'm using it in almost exactly the same
enviroment, Centos 6/Apache 2.2.15/Active Directory...
VirtualHost *:80
Hello,
Thanks to everyone for the feedback and suggestions. I was eventually
able to puzzle out what was going awry. The remaining issues turned out
to be:
1) When proxying was enabled, to trigger an authentication request with
the default Galaxy set-up, I needed to use the “localhost” URL,
On Nov 19, 2012, at 12:49 PM, Harris Shapiro wrote:
Hello,
I'm writing because I've been trying for the past few days to configure
Galaxy to use Apache-based LDAP authentication, but have reached a point
where I'm basically stuck. The system in a virtual machine running:
- CentOS 5.8
