-
Notifications
You must be signed in to change notification settings - Fork 23
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
multi-user access control #3
Comments
There is a nice security implementation for Jena, that work as a interceptor wrapper that calls an application provided check for graph and then for each triple : This URL has disappeared, but there is: The performance is of course diminished, but not too much if putting restrictions at graph level only. |
What has been done for project https://github.com/jmvanel/corporate_risk should be made modular and reusable. |
This use case surfaced recently;
|
One use case is switching to a classical CMS workflow, where article proposals are only visible by content managers.
User U1 must not be able to access data of user U2. We don't need for now a complete Access Control mechanism, like in Virtuoso. A simple API must give access to a Banana-RDF graph store ( dataset ) that contains only data of user U1, and contains also background knowledge and ontologies. This way, it is not possible that a badly writen SPARQL query accesses data of other users. This API could leverage on this utility to create such an in-memory graph store:
This API could be:
The text was updated successfully, but these errors were encountered: