Skip to content
This repository has been archived by the owner on Jan 23, 2024. It is now read-only.

Enforce namespace restrictions #103

Open
MarcusBarnes opened this issue Feb 21, 2017 · 3 comments
Open

Enforce namespace restrictions #103

MarcusBarnes opened this issue Feb 21, 2017 · 3 comments

Comments

@MarcusBarnes
Copy link
Contributor

Currently, the annotation UI does not handle Islandora's Enforce namespace restrictions namespace configuration setting. This would be a potentially useful enhancement when having multiple Drupal instances pointing to the same Fedora commons instance.

@MarcusBarnes
Copy link
Contributor Author

MarcusBarnes commented May 3, 2017

Possibly related to #179.

@kstapelfeldt kstapelfeldt modified the milestones: 7.x-1.9 Release, 7.x -1.10 Release Jun 20, 2017
@kstapelfeldt
Copy link
Member

kstapelfeldt commented Sep 20, 2017

As a user, I expect that when namespace restrictions are applied to a site, I will bring back only annotations with allowed namespaces. We are not sure if this is currently how the software functions. This needs to be tested. We should explore in a multisite and singlesite environment.

Singlesite test: Create a namespace for annotations, create annotations under this namespace, enforce namespace restrictions in Islandora setting, disallowing the annotation namespace, search for a created annotation and see if it is returned.

Also: Return to the annotated object, and see if the object annotation under the restricted namespace appears.

Also: Author XACML policies on the annotation collection and see if these are respected in search and the UI

@kstapelfeldt
Copy link
Member

With the new collection for annotations, we may have another method available for restricting namespaces.

@kimpham54 kimpham54 removed this from the 7.x -1.10 Release milestone Jan 16, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants