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

CKAN dataset authentication to row level #258

Open
debbielee1996 opened this issue Sep 9, 2020 · 0 comments
Open

CKAN dataset authentication to row level #258

debbielee1996 opened this issue Sep 9, 2020 · 0 comments

Comments

@debbielee1996
Copy link

I am thinking of creating authentication for users to view datasets up to the row level e.g. User A can view Table 1 for columns x and y; User B can view Table 1 for columns x.

As I am rather new to CKAN, I would like to check on the design thinking process but would first like to share the environment:

  1. CKAN 2.8
  2. Ubuntu 18.04 LTS
  3. Following extensions installed: Datastore, Datapusher, Filestore, Dataproxy
    I would want users to be able to view remote tables (via Dataproxy) and uploaded CSV files (via Datasotre, Datapusher, Filestore) up to row level based on their individual authentications determined by the admin of the organization they are added to.

Currently this is the design that I came up with but I would like to get some feedback:

Changes in postgresql database
add a new database which will store tables representing each user. Each user table will contain data on which resource it can view and what data columns (or vice versa, store each resource as as a table)

To view
Edit select statement to have changes depending on what user can see (based on the table with user’s access rights). This is in the Dataproxy project's code

When user is assigned to an org
Update table with user’s access rights to every row (by default no access to any unless admin dictates so?)

To update access rights on admin side (front end)
A page for admins to determine what users can view in an organization

Any feedback would be greatly appreciated, thanks!

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

1 participant