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.
Please contact your local Galaxy administrator.
On Mon, May 24, 2010 at 04:14:33PM +0200, Davide Cittaro wrote:That's exactly what I've tried to ask :-)Also, that means that my galaxy user will bedcittaro@ifom-ieo-campus.it . The problem is that email addressdoesn't exist, as usernames defined in LDAP are not the usernames formail addresses... I guess I'll have to study LDAP search syntax andinstruct it to query with my username (dcittaro) and return the emailaddress stripping the domain (davide.cittaro)...
Glad it helped. Here are some Apache Directives that will probably
help:
http://httpd.apache.org/docs/2.2/mod/mod_authnz_ldap.html#authldapremoteuserattribute
which can only legally be one of the attributes included in your:
http://httpd.apache.org/docs/2.2/mod/mod_authnz_ldap.html#authldapurl
That'll let you auth using the 'uid' and set REMOTE_USER to the 'email'.
If the email comes back from LDAP with the @domain.tld already appended
then don't set REMOTE_USER_DOMAIN to anything.
--
Ry4an Brase 612-626-6575
University of Minnesota Supercomputing Institute
for Advanced Computational Research http://www.msi.umn.edu
_______________________________________________
galaxy-dev mailing list
galaxy-dev@lists.bx.psu.edu
http://lists.bx.psu.edu/listinfo/galaxy-dev