[
https://issues.apache.org/jira/browse/JENA-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16595134#comment-16595134
]
ASF GitHub Bot commented on JENA-1594:
--------------------------------------
Github user afs commented on the issue:
https://github.com/apache/jena/pull/465
This is now code-finished. It is still a library that needs code around it
to use.
To make it usable without code, it will need some packaging and setup with
Jetty and documentation about running Jetty securely.
I'd like to get the code in now and follow up on that as a separate pull
request, firstly to expose the new code to people interested by having some
example code while still be clear the code may change in response to feedback,
and secondly so work separating of the webapp Fuseki and core server can happen
without branches complicating things.
> 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)
