It's reasonably easy to set up Galaxy to use external authentication. We modeled our authentication after the way MSI folks did it as posted on the galaxy-dev list a while ago. We use SSO (Single Sign On) with mod_auth_tkt SSO tied into an LDAP back-end used for our cluster. I'd be happy to share the details beyond the LDAP authentication discussion you can find in the Galaxy list archives [1] if necessary. In addition, this sort of question is more appropriate to the galaxy-dev, but not the galaxy-user list.
Regards,
Alex
-- Oleksandr Moskalenko, Ph.D. Biological Applications Support High Performance Computing Center University of Florida
1. http://lists.bx.psu.edu/pipermail/galaxy-dev/2010-May/002660.html http://lists.bx.psu.edu/pipermail/galaxy-dev/2010-May/002667.html
On Oct 26, 2011, at 12:29 PM, Joshua Udall wrote:
Dear Galaxy -
We would like to install and instance of Galaxy on our campus cluster.
The install process looks very straight forward, but tying it in with
our authentication system for the current, functioning cluster may not
be as simple. It appears that galaxy is easy to install if there are
limited users on a local machine or on a cluster where galaxy is the
main use of the cluster (so it handles all the user accounts). Where
would I direct our IT admin group to get more assistance with
customizing the authentication process with our existing, function
cluster?
--
Joshua Udall
Assistant Professor
295 WIDB
Plant and Wildlife Science Dept.
Brigham Young University
Provo, UT 84602
801-422-9307
Fax: 801-422-0008
USA
The Galaxy User list should be used for the discussion of Galaxy analysis and other features on the public server at usegalaxy.org. Please keep all replies on the list by using "reply all" in your mail client. For discussion of local Galaxy instances and the Galaxy source code, please use the Galaxy Development list:
http://lists.bx.psu.edu/listinfo/galaxy-dev
To manage your subscriptions to this and other Galaxy lists, please use the interface at: