Question: user authentication (NIS)
gravatar for FT
3.3 years ago by
FT0 wrote:


I read the doc about external authentication but I'm not sure to understand all of it (I'm a newbie).

I would like to use both capacities of NIS :

 - the use of Linux login and password for access to Galaxy
 - and exploit the system user accounts to the restricted access on file/directory.Importing data would only be possible for an authorized Linux user. Same thing for running tools on data.

I found this old post Standalone Galaxy Server And User Management which is about what I intend to do, but is it possible now ?

Will it change the way Galaxy stores the output of a tool ?
For now my Galaxy instance stores the output in database/files/ in a new directory and probably use the job id to name it. With this authentication will Galaxy create a directory with the user's name and then a subdirectory for each tool output ?


Thank you in advance,


ADD COMMENTlink modified 3.3 years ago • written 3.3 years ago by FT0
gravatar for Hotz, Hans-Rudolf
3.3 years ago by
Hotz, Hans-Rudolf1.8k wrote:

for future reference: PLEASE don't cross-post the same question on galaxy-dev!


Unless you write a special wrapper, Galaxy always stores the data in the same location, independent of the user executing the tool. This is important to ensure several key aspects of the Galaxy framework, like reproducibility and transparency.

Pretty much everything else you ask is more or less possible - although not out of the box, and it might require some work on your side), e.g.:

 - you can work with "data libraries" to restrict access of data to certain users (see: )

- you can restrict (see: or hide (and thereby restrict, see: the tools to specified users.


Regards, Hans-Rudolf


ADD COMMENTlink modified 3.3 years ago by Martin Čech ♦♦ 4.9k • written 3.3 years ago by Hotz, Hans-Rudolf1.8k
gravatar for FT
3.3 years ago by
FT0 wrote:

Thanks for the answer !

Sorry for the cross-post. I thought it might not be the best place for my question since biostar is more on the user side ;)

In fact, the proposed access restrictions for the librairies construction will not be enough for me.
My problem is that the account used to install the instance Galaxy does not have access to all directories (and it is not intended/possible to change that).

As Galaxy accesses files from that account only, its application is limited.

I was wondering if anyone had found a way to connect via a Linux account and launch Galaxy via this account.

ADD COMMENTlink written 3.3 years ago by FT0
Please log in to add an answer.


Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 169 users visited in the last hour