[
https://issues.apache.org/jira/browse/JENA-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071579#comment-17071579
]
Andreas Plank commented on JENA-1874:
-------------------------------------
Well OK, I’ll ask at the user list or I guess I have to.
But if I allow a data set to only allow the read and query methods I would
expect when I press “remove” data set, that it prevents me from doing so or
even better not to provide the “remove” button at all. And for me it seems that
it is not thought of from a developer point of view. Even following the
[documentation case of a read only dataset
(jena.apache.org)|https://jena.apache.org/documentation/fuseki2/fuseki-config-endpoint.html#case-1-read-only-dataset]
it seems read only but is actually not, because pressing the “remove” button
in the manage section does exactly that: removes. This is the critical issue
from my point of view.
Kind regards
Andreas
> How to prevent data set action “remove” for read only sparql data (FUSEKI
> 3.14.0)
> ---------------------------------------------------------------------------------
>
> Key: JENA-1874
> URL: https://issues.apache.org/jira/browse/JENA-1874
> Project: Apache Jena
> Issue Type: Question
> Components: Fuseki
> Affects Versions: Jena 3.14.0
> Reporter: Andreas Plank
> Priority: Critical
>
> Hej-hej,
> Is it possible to get the Fuseki Web app read only where also the manage =>
> remove data set does not apply ?
> I try to get fuseki running with a read-only access to my data set. So far
> I’ve managed to restrict actions on the dataset in
> `configurations/mydataset.ttl`:
> {noformat}
> @prefix : <http://base/#> .
> @prefix tdb: <http://jena.hpl.hp.com/2008/tdb#> .
> @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
> @prefix ja: <http://jena.hpl.hp.com/2005/11/Assembler#> .
> @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
> @prefix fuseki: <http://jena.apache.org/fuseki#> .
> <http://jena.apache.org/2016/tdb#DatasetTDB>
> rdfs:subClassOf ja:RDFDataset .
> ja:DatasetTxnMem rdfs:subClassOf ja:RDFDataset .
> tdb:DatasetTDB rdfs:subClassOf ja:RDFDataset .
> tdb:GraphTDB rdfs:subClassOf ja:Model .
> <http://jena.apache.org/2016/tdb#GraphTDB2>
> rdfs:subClassOf ja:Model .
> ja:MemoryDataset rdfs:subClassOf ja:RDFDataset .
> ja:RDFDatasetZero rdfs:subClassOf ja:RDFDataset .
> <http://jena.apache.org/text#TextDataset>
> rdfs:subClassOf ja:RDFDataset .
> <#service> rdf:type fuseki:Service ;
> fuseki:name "mydataset" ;
> fuseki:serviceQuery "query", "", "sparql";
> fuseki:serviceReadGraphStore "data" ;
> fuseki:dataset :tdb_dataset_read .
> :tdb_dataset_read
> a tdb:DatasetTDB ;
> tdb:location "/fuseki/databases/mydataset" .
> <http://jena.apache.org/2016/tdb#GraphTDB>
> rdfs:subClassOf ja:Model .
> ja:RDFDatasetOne rdfs:subClassOf ja:RDFDataset .
> ja:RDFDatasetSink rdfs:subClassOf ja:RDFDataset .
> <http://jena.apache.org/2016/tdb#DatasetTDB2>
> rdfs:subClassOf ja:RDFDataset .
> {noformat}
> But using the Fuseki interface I can
> # go to manage.html and
> # click on button “remove” and: it’s gone
> How can I prevent the “remove”?
> I know that in my server’s configuration, I can also restrict urls in the
> {{shiro.ini}}, e.g. actions of “update” “upload”, but I can not restrict the
> action of “remove”, can I? I found only that the very DELETE it is done
> somehow over {{/$/datasets/mydataset}} with a DELETE request but I can not
> figure out how to prevent it.
> Thank you,
> Infinite-dao
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
