Hi everyone I'm currently trying to use the API, but I think that our LDAP logging doesn't really help. When I call the script specifying the port in the url, here's what I get: <urlopen error [Errno 111] Connection refused> Then when I don't specify it Here's what I get: HTTP Error 401: Authorization Required <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>401 Authorization Required</title> </head><body> <h1>Authorization Required</h1> <p>This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.</p> <hr> <address>Apache/2.2.3 (CentOS) Server at localhost Port 80</address> </body></html> Did I miss anything? Is there a way to avoid that? Thanks LA
Ok, again sorry for being an idiot. I just had to modify the Apache .conf file related to Galaxy. For the time being I allowed everyone on the API (since it's not accessible via the Internet it's allright) so the "all" will eventually be changed but here is what I added in the file: <Location /galaxy-dev> AuthName "Galaxy (development)" AuthType Basic AuthBasicProvider ldap AuthLDAPURL "ldap://ocs.embl.org/cn=Users,dc=embl,dc=org?uid" AuthzLDAPAuthoritative off Require valid-user </Location> <Location /galaxy-dev/api> AuthName "Galaxy (API)" AuthType Basic AuthBasicProvider ldap AuthLDAPURL "ldap://ocs.embl.org/cn=Users,dc=embl,dc=org?uid" AuthzLDAPAuthoritative off Satisfy any Allow from all </Location> L-A Le 17/06/2011 14:14, Louise-Amélie Schmitt a écrit :
Hi everyone
I'm currently trying to use the API, but I think that our LDAP logging doesn't really help.
When I call the script specifying the port in the url, here's what I get:
<urlopen error [Errno 111] Connection refused>
Then when I don't specify it Here's what I get:
HTTP Error 401: Authorization Required <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>401 Authorization Required</title> </head><body> <h1>Authorization Required</h1> <p>This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.</p> <hr> <address>Apache/2.2.3 (CentOS) Server at localhost Port 80</address> </body></html>
Did I miss anything? Is there a way to avoid that?
Thanks LA
___________________________________________________________ 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:
Louise-Amélie Schmitt wrote:
Ok, again sorry for being an idiot.
I just had to modify the Apache .conf file related to Galaxy.
For the time being I allowed everyone on the API (since it's not accessible via the Internet it's allright) so the "all" will eventually be changed but here is what I added in the file:
<Location /galaxy-dev> AuthName "Galaxy (development)" AuthType Basic AuthBasicProvider ldap AuthLDAPURL "ldap://ocs.embl.org/cn=Users,dc=embl,dc=org?uid" AuthzLDAPAuthoritative off Require valid-user </Location> <Location /galaxy-dev/api> AuthName "Galaxy (API)" AuthType Basic AuthBasicProvider ldap AuthLDAPURL "ldap://ocs.embl.org/cn=Users,dc=embl,dc=org?uid" AuthzLDAPAuthoritative off Satisfy any Allow from all </Location>
Hi L-A, I was about to reply, but you figured it out just in time. This is not inherently unsafe since everything behind the /api route requires an API key. --nate
L-A
Le 17/06/2011 14:14, Louise-Amélie Schmitt a écrit :
Hi everyone
I'm currently trying to use the API, but I think that our LDAP logging doesn't really help.
When I call the script specifying the port in the url, here's what I get:
<urlopen error [Errno 111] Connection refused>
Then when I don't specify it Here's what I get:
HTTP Error 401: Authorization Required <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>401 Authorization Required</title> </head><body> <h1>Authorization Required</h1> <p>This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.</p> <hr> <address>Apache/2.2.3 (CentOS) Server at localhost Port 80</address> </body></html>
Did I miss anything? Is there a way to avoid that?
Thanks LA
___________________________________________________________ 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:
___________________________________________________________ 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:
Le 17/06/2011 16:50, Nate Coraor a écrit :
Louise-Amélie Schmitt wrote:
Ok, again sorry for being an idiot.
I just had to modify the Apache .conf file related to Galaxy.
For the time being I allowed everyone on the API (since it's not accessible via the Internet it's allright) so the "all" will eventually be changed but here is what I added in the file:
<Location /galaxy-dev> AuthName "Galaxy (development)" AuthType Basic AuthBasicProvider ldap AuthLDAPURL "ldap://ocs.embl.org/cn=Users,dc=embl,dc=org?uid" AuthzLDAPAuthoritative off Require valid-user </Location> <Location /galaxy-dev/api> AuthName "Galaxy (API)" AuthType Basic AuthBasicProvider ldap AuthLDAPURL "ldap://ocs.embl.org/cn=Users,dc=embl,dc=org?uid" AuthzLDAPAuthoritative off Satisfy any Allow from all </Location> Hi L-A,
I was about to reply, but you figured it out just in time. This is not inherently unsafe since everything behind the /api route requires an API key.
--nate
Ok, I'll leave it like that then, thanks! L-A
L-A
Le 17/06/2011 14:14, Louise-Amélie Schmitt a écrit :
Hi everyone
I'm currently trying to use the API, but I think that our LDAP logging doesn't really help.
When I call the script specifying the port in the url, here's what I get:
<urlopen error [Errno 111] Connection refused>
Then when I don't specify it Here's what I get:
HTTP Error 401: Authorization Required <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>401 Authorization Required</title> </head><body> <h1>Authorization Required</h1> <p>This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.</p> <hr> <address>Apache/2.2.3 (CentOS) Server at localhost Port 80</address> </body></html>
Did I miss anything? Is there a way to avoid that?
Thanks LA
___________________________________________________________ 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:
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:
participants (2)
-
Louise-Amélie Schmitt -
Nate Coraor