[ https://issues.apache.org/jira/browse/JENA-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598656#comment-16598656 ]
ASF subversion and git services commented on JENA-1594: ------------------------------------------------------- Commit c8a31476d4072b44790965d5d79963c545e6c2ec in jena's branch refs/heads/master from [~an...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=c8a3147 ] JENA-1594: Merge commit 'refs/pull/465/head' of https://github.com/apache/jena This closes #465. > Provide per-graph access control in Fuseki > ------------------------------------------ > > Key: JENA-1594 > URL: https://issues.apache.org/jira/browse/JENA-1594 > Project: Apache Jena > Issue Type: Task > Components: Fuseki > Affects Versions: Jena 3.8.0 > Reporter: Andy Seaborne > Assignee: Andy Seaborne > Priority: Major > > This will be for TDB1 and TDB2 only. They provide a [filter > mechanism|https://jena.apache.org/documentation/tdb/quadfilter.html] so that > triples and quads are filtered out at the lowest level. > This first version of data security will be for a data-access controlled > read-only service. The expectation is that updates happens via a different > Fuseki service sharing the same database and that service is service-access > controlled (i.e all or nothing access). > The data-access controlled service takes a security configuration of a > collection of graph names. Only those graph are visible through the > data-access controlled service. > For the union default graph, it is the union of visible graph only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)