Standalone galaxy server and user management
Hi, we want to use a standalone Galaxy server here and integrate that with our Sun Grinengine cluster. While I could find information on how to do that I also want to know if it's possible to use our local user database (NIS based) to manage the galaxy users and make their galaxy scripts running with their userid. Could somebody tell me if that is a) easy b) hard c) impossible regards, Andreas
Andreas Kuntzagk wrote:
we want to use a standalone Galaxy server here and integrate that with our Sun Grinengine cluster. While I could find information on how to do that I also want to know if it's possible to use our local user database (NIS based) to manage the galaxy users and make their galaxy scripts running with their userid. Could somebody tell me if that is a) easy b) hard c) impossible
Hi Andreas, Mostly "impossible" at present, as in code to do it does not yet exist. However, it's been requested by numerous users, so it's on our roadmap. I've created an issue for it in our tracker: http://bitbucket.org/galaxy/galaxy-central/issue/106/ --nate
Hi,
we want to use a standalone Galaxy server here and integrate that with our Sun Grinengine cluster. While I could find information on how to do that I also want to know if it's possible to use our local user database (NIS based) to manage the galaxy users and make their galaxy scripts running with their userid. Could somebody tell me if that is a) easy b) hard c) impossible
Hi Andreas,
Mostly "impossible" at present, as in code to do it does not yet exist. However, it's been requested by numerous users, so it's on our roadmap. I've created an issue for it in our tracker:
from this issue I gleam that at least the first part (use a local user database) should be possible: "Some Galaxy installations tightly integrate Galaxy users with system users." Could you point me to any docs describing this? Thanks, Andreas
Andreas Kuntzagk wrote:
from this issue I gleam that at least the first part (use a local user database) should be possible: "Some Galaxy installations tightly integrate Galaxy users with system users."
Could you point me to any docs describing this?
Authentication is available via anything that Apache supports (in your case with NIS, probably mod_auth_pam). Instructions on setting up an Apache proxy (and authentication) are in the wiki here: http://g2.trac.bx.psu.edu/wiki/HowToInstall/ApacheProxy --nate
Authentication is available via anything that Apache supports (in your case with NIS, probably mod_auth_pam). Instructions on setting up an Apache proxy (and authentication) are in the wiki here:
Ok. I was running the standalone server. So I need to use Apache as proxy. Does that mean I still have the Galaxy run.sh running and a separate Apache forwarding all request to Galaxy? I think I have to reread that wiki page a few times to understand all of it ;-) regards, Andreas
Andreas Kuntzagk wrote:
Ok. I was running the standalone server. So I need to use Apache as proxy. Does that mean I still have the Galaxy run.sh running and a separate Apache forwarding all request to Galaxy?
I think I have to reread that wiki page a few times to understand all of it ;-)
That is correct. You don't need the stuff in the "Apache configuration with Galaxy not at the web server root" or "Display at UCSC" sections unless you actually need to do as titled. --nate
from this issue I gleam that at least the first part (use a local user database) should be possible: "Some Galaxy installations tightly integrate Galaxy users with system users."
Could you point me to any docs describing this? Hi, I think you are looking for this:
http://g2.trac.bx.psu.edu/wiki/HowToInstall/ApacheProxy scroll to: External authentication best, ido
participants (3)
-
Andreas Kuntzagk -
Ido M. Tamir -
Nate Coraor