Skip to content
Permalink
Browse files
Update oak-doc/src/site/markdown/security/authorization/bestpractices.md
Co-authored-by: Jörg Hoh <joerghoh@users.noreply.github.com>
  • Loading branch information
anchela and joerghoh committed May 18, 2022
1 parent f17b4ec commit cf7f1a04b1acc67e3a9686804792a1b694d4fbbe
Showing 1 changed file with 1 addition and 1 deletion.
@@ -36,7 +36,7 @@ The following references provide a good overview as well as guidance on how to b
### Content Modelling

As suggested in [Jackrabbbit Wiki](https://jackrabbit.apache.org/archive/wiki/JCR/DavidsModel_115513389.html#DavidsModel-Rule#2:Drivethecontenthierarchy,don'tletithappen)
the content hierarchy in your JCR repository should be designed and access control requirements tend to be a good driver.
the content hierarchy in your JCR repository should be designed and not just happen. Access control requirements tend to be a good driver.

Make sure the content design allows for a readable and manageable access control setup later on to secure your data.
Excessive complexity is often a strong indicator for problems with your content model, making its security error prone

0 comments on commit cf7f1a0

Please sign in to comment.