This is an automated email from the ASF dual-hosted git repository. enorman pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/sling-site.git
commit 3ec9a44dcdec4e051e09e36d96027358a39e7947 Author: Eric Norman <[email protected]> AuthorDate: Fri Feb 4 13:30:35 2022 -0800 SLING-11034 document the configuration option To expose nested authorizable properties as child resources --- .../managing-users-and-groups-jackrabbit-usermanager.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/main/jbake/content/documentation/bundles/managing-users-and-groups-jackrabbit-usermanager.md b/src/main/jbake/content/documentation/bundles/managing-users-and-groups-jackrabbit-usermanager.md index e5eb715..9ae472f 100644 --- a/src/main/jbake/content/documentation/bundles/managing-users-and-groups-jackrabbit-usermanager.md +++ b/src/main/jbake/content/documentation/bundles/managing-users-and-groups-jackrabbit-usermanager.md @@ -405,3 +405,15 @@ Additionally, the following service interfaces may be implemented by a custom OS 2. **org.apache.sling.jackrabbit.usermanager.PrincipalNameGenerator** - An implementation of this service interface allows to fully customize principal name generation +#### Enabling the option to expose nested authorizable property containers as child resources + +*Since Version 2.2.18* + +By default, the nested authorizable property containers are not exposed as child resources. This behavior may be enabled via configuration. + +For example: + + "org.apache.sling.jackrabbit.usermanager.impl.resource.AuthorizableResourceProvider":{ + "resources.for.nested.properties":true + } +
