[ckan-dev] fine grain access control

Knud Möller knud at datalysator.com
Fri Jun 24 12:50:04 UTC 2016


Hi Richard,

I couldn’t tell you in detail how to implement the scenario you outline,
but generally speaking the IAuthFunctions interface [1] is what you need.
The documentation is not very detailed, unfortunately. We have implemented
some rather heavy-handed code for a CKAN plugin [2] that prevents anonymous
users from seeing anything at all. See in particular get_auth_functions()
and berlin_site_read().

Cheers,
Knud

[1]
http://docs.ckan.org/en/latest/extensions/plugin-interfaces.html#ckan.plugins.interfaces.IAuthFunctions
[2]
https://github.com/berlinonline/ckanext-berlin/blob/dev-ckan_2_4/ckanext/berlin/plugin.py


On 23 June 2016 at 22:52:55, Richard Skeggs (rickskeggs at gmail.com) wrote:

I have installed CKAN 2.5 onto a linux Ubuntu 14.04 server. The website
talks about CKAN being able to support fine grain access controls but I can
find the implementation details.

The scenario I am trying to get to is:

- All users can perform searches regardless of whether they are signed into
CKAN.
- All the meta data is returned for results that fulfil the search
criteria.
- To download any data from CKAN the users must be registered and logged
into the site.
- Then for some results only specially identified users can access the
underlying dataset.

Any pointers to documentation or code would be most welcome.

Thanks


_______________________________________________
ckan-dev mailing list
ckan-dev at lists.okfn.org
https://lists.okfn.org/mailman/listinfo/ckan-dev
Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev


-- 
Dr. Knud Hinnerk Möller
Datalysator - Web Data Solutions and Training
knud at datalysator.com
+49 151 46 44 83 25
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20160624/34af5591/attachment-0003.html>


More information about the ckan-dev mailing list