I am not aware of Galaxy having any sort of login hook as you
described --- without writing custom code. This brings up the added
challenge of keeping your custom modifications current with the latest
release of galaxy.
Another approach, and I am not sure how feasible this is on your
setup, is to create all these added services during the user
creation process. On our HPC cluster this is the method we
implemented. All our users can use SFTP, rsync, BBCP, etc to upload to
the cluster and the user moves their data to galaxy by the "FTP
Trick" to their "dropbox" folder that galaxy has access to. Once
data is moved to the dropbox folder, users login via the galaxy web
interface and select the data via the Get Data -> Upload File
This might be a simpler approach, create these services for each new
user during their account creation. You will be forced to use the
command line interface to create new users, but I believe its far
simpler then using postgres notify or the other methods you described.
Computer Science, Undergraduate Student
Donald Bren School of Information and Computer Sciences
Research Computing Support
Office of Information Technology
University of California, Irvine
On Sun, Aug 25, 2013 at 9:39 AM, Maddhi, Srinivas
> Does Galaxy provide a post-login hook that could be used to trigger an
> operating system level action upon successful login ?
> Here is the scenario and use-case where that would come in handy:
> * Local instance of Galaxy (Nov 2012 release) on a Linux server with a
> PostgreSQL DB
> * Upload via FTP feature is enabled
> * Users are authenticated via LDAP and nginx
> * Users should be able to securely upload files (to their sub-directory
> within the configured FTP upload directory)
> The current method being employed to fulfill this use-case is through a
> modification to Š/galaxy-dist/lib/galaxy/web/framework/__init__.py file
> that calls a a shell script which creates an OS-level user and associated
> FTP upload directory. Files are uploaded by users via sFTP (SSHD
> configured to restrict Galaxy users to a chroot'ed directory).
> Options considered:
> * Shell/Python script that periodically queries the "galaxy_user" table
> and creates an OS-level user and FTP upload directory (not yet tried;
> introduces delay between user creation and FTP capability unless frequency
> of polling is high)
> * ProFTPD with sFTP and LDAP modules (increased administrative overhead
> compared to using built-in SSHD; wasn't able to get auto directory
> creation to work due to TBD cause)
> * PostgreSQL listen-notify to call a sFTP user creation script when an
> insert occurs in the "galaxy_user" table (not yet tried)
> Thank you.
> Senior Systems Administrator
> Iowa Institute for Human Genetics
> ITS Research Services, The University of Iowa
> 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:
> To search Galaxy mailing lists use the unified search 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:
To search Galaxy mailing lists use the unified search at: