You are not allowed to access this dataset

Question: You are not allowed to access this dataset

2.2 years ago by

France

Hello everyone !

I have a strange behaviour on my histories and it is troublesome since it affects several hundreds of them. I am working on a local instance of Galaxy release 16.01.

I modified permissions of some data input of my workflow including a bed file.Now when I try to access to one of my input I have this 2 messages :

In the History Panel on the right:

An error occurred while getting updates from the server. Please contact a Galaxy administrator if the problem persists. Details

And where the data should be displayed :

You are not allowed to access this dataset

This file is obtained after several computations from the bed file. So all the files generated directly from this bed file are affected. After the permission modification I have access again to the first bed file, but not to these result files.

I looked with bioblend but I didn't find a way to modify permission of a dataset within an history. I looked in the postgresql DB directly but I think this is not a good idea. I would like to avoid to launch again the workflow for each patient.

How could I modify this permission please ?

Thank you for your help !

PS : I don't have access to "Edit Attribute" buttons, and there are too many histories to make this one by one.

admin local dataset permissions • 881 views

ADD COMMENT • link •

modified 2.2 years ago by Jennifer Hillman Jackson ♦ 25k • written 2.2 years ago by christophe.habib • 340

When I click on Edit attribute I have this error :

You do not have permission to edit this dataset's ( id: 08d609333a4b912f ) information.

I just tried to access to the dataset with Bioblend :

gi.dataset.show_dataset(datasetID,hda_ldda="ldda")

And I have this error :

u'400 Bad Request\nThe server could not comply with the request since\r\nit is either malformed or otherwise incorrect.\r\n\nInvalid LibraryDatasetDatasetAssociation id ( 08d609333a4b912f ) specified\n'

ADD REPLY • link modified 2.2 years ago • written 2.2 years ago by christophe.habib • 340

Christopher seems to have solved this issue as described here: https://botbot.me/freenode/galaxyproject/2016-09-06/?msg=72554898&page=1

I just gave access again to the old role, and then I used new roles to make the access more specific (I had 1 role per lab, i needed to make 1 role per disease since each data library is related to one disease only) So now the data libraries are accessible by "lab" and "disease", so the old histories datasets can be accessible

ADD REPLY • link written 2.2 years ago by Martin Čech ♦♦ 4.9k

2.2 years ago by

Jennifer Hillman Jackson ♦ 25k

United States

Jennifer Hillman Jackson ♦ 25k wrote:

Hello,

The permissions are likely a mismatch between the account used and the permissions assigned. Please double check this by clicking on the pencil icon for the dataset (one at a time) to reach the Edit Attributes forms, then the Permissions tab, and review. Perhaps the datasets had permissions set then the history containing them was shared with another account (the one used with BioBlend)?

The Galaxy version in use is much older than the current release. Upgrading to 16.07 may also be a solution as many upgrades, including Admin upgrades and bug fixes, occur at each release. For the first error, this indicates that the database should be upgraded to handle the processing load.

How to:

https://wiki.galaxyproject.org/Learn/SecurityFeatures
http://getgalaxy.org
https://docs.galaxyproject.org/en/master/releases/16.07_announce.html
https://wiki.galaxyproject.org/Admin/Maintenance
https://wiki.galaxyproject.org/Admin/Config/Performance/ProductionServer#Switching_to_a_database_server (note this is best done with a new Galaxy instance - data is difficult to migrate between the default SQLite database and the others, more https://biostar.usegalaxy.org/p/19295)

Let us know if you continue to have problems after confirming permissions and upgrading and we can troubleshoot from there.

Jen, Galaxy team

ADD COMMENT • link modified 2.2 years ago • written 2.2 years ago by Jennifer Hillman Jackson ♦ 25k

Update: I see the comments in galaxyproject IRC. This was a prior issue that seems to be resolved. Is the latest issue resolved? Thanks!

ADD REPLY • link modified 2.2 years ago • written 2.2 years ago by Jennifer Hillman Jackson ♦ 25k

Thanks for your answer. This problem was solved indeed. I have another issue and I am writing a new post to give as much details as possible. But indeed both problem (the old one here and the new one) are related to the same file.

ADD REPLY • link written 2.2 years ago by christophe.habib • 340

Similar posts • Search »