Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A regular user can place his organization under any organization #1633

Closed
Vilsepi opened this issue Apr 4, 2014 · 4 comments
Closed

A regular user can place his organization under any organization #1633

Vilsepi opened this issue Apr 4, 2014 · 4 comments
Assignees

Comments

@Vilsepi
Copy link

Vilsepi commented Apr 4, 2014

We are using CKAN 2.2 with code from the ckanext-hierachy to provide a UI for handling organization hierarchy.

It seems that a regular user (without sysadmin rights) is able to select any organization as the parent organization. Consider userAlice who has created organization cutePets, and then userEve who has created organization bunnySlaughterhouse. Now userEve can move her organization to be a suborganization of cutePets, and to the rest of the users, this looks like a valid, "official" suborganization.

I am not sure whether this is by design or a bug, but we have a case where we cannot completely trust every CKAN user, and thus it would probably be better if users can only select those organizations in which they are already admins.

@davidread
Copy link
Contributor

It's working as it was designed. The parent org's admin will automatically get admin power for the sub-organization. But all the same you're right about conferring officialness.

I suggest that we require the user to be admin for the parent.

@amercader amercader added this to the CKAN 2.4 milestone Oct 22, 2014
@amercader
Copy link
Member

@davidread is this something that needs to be fixed on ckanext-hierachy? If so can you please move the issue there and close this one? Cheers.

@davidread
Copy link
Contributor

The code for this is in ckan, so let's leave the issue here.

I think this a worthwhile improvement so will try and get round to doing it.

@rossjones
Copy link
Contributor

This issue is being closed as it is nearly more than 18 months old. If you are still experiencing this problem and wish to help investigate further, or submit a PR, please feel free to re-open it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants