Contributor role assigned at sub-dataverse level blocks accessed to contained datasets (even when Contributor role also assigned at dataset)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
What steps does it take to reproduce the issue?
Create a sub-dataverse - do not publish.
Assign a user Contributor role at sub-dataverse.
Create one or more datasets in that sub-dataverse. Do not publish.
In dataverse ui, it looks like the contributor role for the dataset is inherited for the contained datasets.
User attempts to access sub-dataverse - they get the "Permission denied" error message.
User attempts to access the contained datasets - they get the "Permission denied" error message.
Assign the user Contributor role for each contained dataset.
User attempts to access sub-dataverse - still get "Permission denied" error message.
Remove the user's Contributor role at the sub-dataverse level (leave their Contributor role for the datasets).
User can access the dataset and Edit metadata and Ts&Cs and submit for review.
-
When does this issue occur?
When Contributor role is assigned at sub-dataverse level. -
Which page(s) does it occurs on?
See above -
What happens?
See above -
To whom does it occur (all users, curators, superusers)?
Contributors assigned at sub-dataverse level -
What did you expect to happen?
I would expect either:
- As the UI seems to indicate that the Contributor role is inherited from the sub-dataverse, that assigning Contributor role at the sub-dataverse gives the user the Contributor role/permissions for the contained datasets. Certainly don't completely block access to the datasets.
Or:
- If the Contributor role is only applicable to datasets, do not allow the Contributor role to be assigned at a sub-dataverse level and allow only for datasets.
Which version of Dataverse are you using?
6.3
Any related open or closed issues to this bug report?
Not sure.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the scenario in Dataverse 6.3 by assigning Contributor at the sub-dataverse level, then compare access to the sub-dataverse and contained datasets with dataset-level assignments. Trace the authorization path for inherited Contributor permissions and define done as allowing the expected access or preventing the invalid role assignment, with regression coverage for both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authorization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100