This is an automated email from the ASF dual-hosted git repository. andy pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/jena-site.git
commit a433412b992bc64dbb8cdc5fc7515ea68fb84ad7 Author: Andy Seaborne <[email protected]> AuthorDate: Tue Jul 15 11:51:08 2025 +0100 Unlink jena-permissions; add notice of removal --- layouts/_default/baseof.html | 2 -- source/documentation/__index.md | 1 - source/documentation/fuseki2/fuseki-security.md | 6 ------ source/documentation/javadoc.md | 1 - source/documentation/permissions/__index.md | 2 ++ source/documentation/permissions/assembler.md | 2 ++ source/documentation/permissions/design.md | 2 ++ source/documentation/permissions/evaluator.md | 2 ++ source/documentation/permissions/example.md | 2 ++ source/documentation/permissions/migration2To3.md | 2 ++ source/download/maven.md | 5 ----- 11 files changed, 12 insertions(+), 15 deletions(-) diff --git a/layouts/_default/baseof.html b/layouts/_default/baseof.html index a5bbdb73e..cf9fc5a85 100644 --- a/layouts/_default/baseof.html +++ b/layouts/_default/baseof.html @@ -69,7 +69,6 @@ <li><a class="dropdown-item" href="/documentation/geosparql/index.html">GeoSPARQL</a></li> <li><a class="dropdown-item" href="/documentation/inference/index.html">Inference API</a></li> <li><a class="dropdown-item" href="/documentation/ontology/">Ontology API</a></li> - <li><a class="dropdown-item" href="/documentation/permissions/index.html">Permissions</a></li> <li><a class="dropdown-item" href="/documentation/extras/querybuilder/index.html">Query Builder</a></li> <li><a class="dropdown-item" href="/documentation/rdf/index.html">RDF API</a></li> <li><a class="dropdown-item" href="/documentation/rdfconnection/">RDF Connection - SPARQL API</a></li> @@ -94,7 +93,6 @@ <li><a class="dropdown-item" href="/documentation/javadoc/shex/">ShEx</a></li> <li><a class="dropdown-item" href="/documentation/javadoc/tdb2/">TDB</a></li> <li><a class="dropdown-item" href="/documentation/javadoc/text/">Text Search</a></li> - <li><a class="dropdown-item" href="/documentation/javadoc/permissions/">Permissions</a></li> <li><a class="dropdown-item" href="/documentation/javadoc/extras/querybuilder/">Query Builder</a></li> <li><a class="dropdown-item" href="/documentation/javadoc/geosparql/">GeoSPARQL</a></li> </ul> diff --git a/source/documentation/__index.md b/source/documentation/__index.md index 98ad13295..e8a10540e 100644 --- a/source/documentation/__index.md +++ b/source/documentation/__index.md @@ -25,7 +25,6 @@ sections. * [ShEx](./shex) - ShEx processor for Jena * [Text Search](./query/text-query.html) - enhanced indexes using Lucene for more efficient searching of text literals in Jena models and datasets. * [GeoSPARQL](./geosparql/) - support for GeoSPARQL -* [Permissions](./permissions/) - a permissions wrapper around Jena RDF implementation * [Tools](./tools/) - various command-line tools and utilities to help developers manage RDF data and other aspects of Jena * [How-To's](./notes/) - various topic-specific how-to documents * [QueryBuilder](./extras/querybuilder/) - Classes to simplify the programmatic building of various query and update statements. diff --git a/source/documentation/fuseki2/fuseki-security.md b/source/documentation/fuseki2/fuseki-security.md index 3f5b59a8b..ff82cdd16 100644 --- a/source/documentation/fuseki2/fuseki-security.md +++ b/source/documentation/fuseki2/fuseki-security.md @@ -14,12 +14,6 @@ administrative functions are limited to `localhost`. One can access it via `127.0.0.1` (IPv4), or `[::1]` (IPv6). Access from an external machine is not considered as localhost and thus restricted. -Once Shiro has been configured to perform user authentication it provides a -good foundation on which the [Jena Permissions](../permissions/) layer can be -configured. There is an [example implementation](../permissions/example.html) -documented in the Jena Permissions section. The Jena Permissions layer can be -used to restrict access to specific graphs or triples within graphs. - A simple example to enable basic user/password authentication is shown in the default `shiro.ini` configuration. The default admin user is `admin` and the password is `pw`. This can be changed directly in the INI file. Note that this diff --git a/source/documentation/javadoc.md b/source/documentation/javadoc.md index f9e4500fa..1d927673c 100644 --- a/source/documentation/javadoc.md +++ b/source/documentation/javadoc.md @@ -17,4 +17,3 @@ title: Jena JavaDoc - [GeoSPARQL](javadoc/geosparql/index.html) - [Query Builder](javadoc/extras/querybuilder/index.html) - [Service Enhancer](javadoc/extras/serviceenhancer/index.html) -- [Security Permissions JavaDoc](javadoc/permissions/index.html) diff --git a/source/documentation/permissions/__index.md b/source/documentation/permissions/__index.md index ebc0fd8e8..eaa3ec57c 100644 --- a/source/documentation/permissions/__index.md +++ b/source/documentation/permissions/__index.md @@ -3,6 +3,8 @@ title: Jena Permissions - A Permissions wrapper around the Jena RDF implementati slug: index --- +> The jena-permissions subsystem is planned for removal at Jena 6.0.0. + Jena Permissions is a SecurityEvaluator interface and a set of dynamic proxies that apply that interface to Jena Graphs, Models, and associated methods and classes. It does not implement any specific security policy but provides a framework for developers or integrators to implement any desired policy. ## Documentation diff --git a/source/documentation/permissions/assembler.md b/source/documentation/permissions/assembler.md index ae534a9a5..76dd59b0a 100644 --- a/source/documentation/permissions/assembler.md +++ b/source/documentation/permissions/assembler.md @@ -2,6 +2,8 @@ title: Jena Permissions - Assembler for a Secured Model --- +> The jena-permissions subsystem is planned for removal at Jena 6.0.0. + Jena Permissions provides a standard Jena assembler making it easy to use the `SecuredModel` in an Assembler based environment. To use the permissions assembler the assembler file must contain the lines: [] ja:loadClass "org.apache.jena.permissions.SecuredAssembler" . diff --git a/source/documentation/permissions/design.md b/source/documentation/permissions/design.md index 6a6f14ca5..292badc2b 100644 --- a/source/documentation/permissions/design.md +++ b/source/documentation/permissions/design.md @@ -2,6 +2,8 @@ title: Jena Permissions - Design --- +> The jena-permissions subsystem is planned for removal at Jena 6.0.0. + Jena Permissions is designed to allow integrators to implement almost any security policy. Fundamentally it works by implementing dynamic proxies on top of the Jena Graph and Model interfaces as well as objects returned by those interfaces. The proxy verifies that the actions on those objects are permitted by the policy before allowing the actions to proceed. The graph or model is created by the `org.apache.jena.permissions.Factory` object by wrapping a Graph or Model implementation and associating it with a URI (`graphIRI`) and a SecurityEvaluator implementation. The `graphIRI` is the URI that will be used to identify the graph/model to the security evaluator. diff --git a/source/documentation/permissions/evaluator.md b/source/documentation/permissions/evaluator.md index 8687d5686..5a1cfb779 100644 --- a/source/documentation/permissions/evaluator.md +++ b/source/documentation/permissions/evaluator.md @@ -2,6 +2,8 @@ title: Jena Permissions - SecurityEvaluator implementation --- +> The jena-permissions subsystem is planned for removal at Jena 6.0.0. + ## Overview The SecurityEvaluator interface defines the access control operations. It provides the interface between the authentication (answers the question: "who are you?") and the authorization (answers the question: "what can you do?"), as such it provides access to the current principal (user). The javadocs contain detailed requirements for implementations of the SecurityEvaluator interface, short notes are provided below. diff --git a/source/documentation/permissions/example.md b/source/documentation/permissions/example.md index 0d09cde7f..545cebea4 100644 --- a/source/documentation/permissions/example.md +++ b/source/documentation/permissions/example.md @@ -2,6 +2,8 @@ title: Adding Jena Permissions to Fuseki --- +> The jena-permissions subsystem is planned for removal at Jena 6.0.0. + ## Overview The goal of this document is to add Jena Permissions to a fuseki deployment to restrict access to graph data. This example will take the example application, deploy the data to a fuseki instance and add the Jena Permissions to achieve the same access restrictions that the example application has. diff --git a/source/documentation/permissions/migration2To3.md b/source/documentation/permissions/migration2To3.md index bcf146ea4..5d73d4a35 100644 --- a/source/documentation/permissions/migration2To3.md +++ b/source/documentation/permissions/migration2To3.md @@ -2,6 +2,8 @@ title: "Jena Permissions - Migration notes: Version 2.x to Version 3.x" --- +> The jena-permissions subsystem is planned for removal at Jena 6.0.0. + When Jena moved from version 2 to version 3 there was a major renaming of packages. One of the packages renamed was the Jena Permissions package. It was formerly named Jena Security. There are several changes that need to occur to migrate from jena-security version 2.x to jena-permissions version 3.x. Changes diff --git a/source/download/maven.md b/source/download/maven.md index c88b6fdb9..6474eb1ab 100644 --- a/source/download/maven.md +++ b/source/download/maven.md @@ -115,11 +115,6 @@ structuring Jena development. <td>A utility package to simplify the building of ARQ queries in code. </td> </tr> - <tr> - <td><code>jena-permissions</code></td> - <td><code>jar</code></td> - <td>Security wrapper around Jena RDF implementation.</td> - </tr> </table> There are also a number of artifacts used in development.
