From edd1915d1bd06d7d05f9f9c7da43c23ec72008e5 Mon Sep 17 00:00:00 2001 From: Wilson-Emmanuel Date: Thu, 24 Nov 2022 10:56:28 +0900 Subject: [PATCH 1/2] Corrected errors on the ACLS document Closes gh-12270 --- .../modules/ROOT/pages/servlet/authorization/acls.adoc | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/modules/ROOT/pages/servlet/authorization/acls.adoc b/docs/modules/ROOT/pages/servlet/authorization/acls.adoc index fe700366bf..0ae270c6c8 100644 --- a/docs/modules/ROOT/pages/servlet/authorization/acls.adoc +++ b/docs/modules/ROOT/pages/servlet/authorization/acls.adoc @@ -65,12 +65,12 @@ When used in the context of receiving a permission, an SID is generally called a The only columns are the ID and the Java class name. Thus, there is a single row for each unique Class for which we wish to store ACL permissions. -* Finally, `ACL_ENTRY` stores the individual permissions assigned to each recipient. -Columns include a foreign key to the ACL_OBJECT_IDENTITY, the recipient (which is a foreign key to ACL_SID), whether we audit or not, and the integer bit mask that represents the actual permission being granted or denied. -We have a single row for every domain object instance for which we store ACL permissions. +* `ACL_OBJECT_IDENTITY` stores information for each unique domain object instance in the system. +Columns include a primary key ID, a foreign key to the `ACL_CLASS` table, a unique identifier so we know which ACL_CLASS instance we're providing information for, the parent, a foreign key to the `ACL_SID` table to represent the owner of the domain object instance, and whether we allow ACL entries to inherit from any parent ACL. +We have a single row for every domain object instance we're storing ACL permissions for. -* Finally, ACL_ENTRY stores the individual permissions assigned to each recipient. -Columns include a foreign key to the ACL_OBJECT_IDENTITY, the recipient (i.e. a foreign key to ACL_SID), whether we'll be auditing or not, and the integer bit mask that represents the actual permission being granted or denied. +* Finally, `ACL_ENTRY` stores the individual permissions assigned to each recipient. +Columns include a foreign key to the `ACL_OBJECT_IDENTITY`, the recipient (i.e. a foreign key to ACL_SID), whether we'll be auditing or not, and the integer bit mask that represents the actual permission being granted or denied. We have a single row for every recipient that receives a permission to work with a domain object. From ed657a8fac70d34f072d5f782a912c96d04c0c7d Mon Sep 17 00:00:00 2001 From: Steve Riesenberg Date: Thu, 15 Dec 2022 14:15:30 -0600 Subject: [PATCH 2/2] Polish gh-12280 Apply editing changes from gh-9668 --- docs/modules/ROOT/pages/servlet/authorization/acls.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/modules/ROOT/pages/servlet/authorization/acls.adoc b/docs/modules/ROOT/pages/servlet/authorization/acls.adoc index 0ae270c6c8..5811e8d373 100644 --- a/docs/modules/ROOT/pages/servlet/authorization/acls.adoc +++ b/docs/modules/ROOT/pages/servlet/authorization/acls.adoc @@ -66,8 +66,8 @@ The only columns are the ID and the Java class name. Thus, there is a single row for each unique Class for which we wish to store ACL permissions. * `ACL_OBJECT_IDENTITY` stores information for each unique domain object instance in the system. -Columns include a primary key ID, a foreign key to the `ACL_CLASS` table, a unique identifier so we know which ACL_CLASS instance we're providing information for, the parent, a foreign key to the `ACL_SID` table to represent the owner of the domain object instance, and whether we allow ACL entries to inherit from any parent ACL. -We have a single row for every domain object instance we're storing ACL permissions for. +Columns include the ID, a foreign key to the ACL_CLASS table, a unique identifier so we know the ACL_CLASS instance for which we provide information, the parent, a foreign key to the ACL_SID table to represent the owner of the domain object instance, and whether we allow ACL entries to inherit from any parent ACL. +We have a single row for every domain object instance for which we store ACL permissions. * Finally, `ACL_ENTRY` stores the individual permissions assigned to each recipient. Columns include a foreign key to the `ACL_OBJECT_IDENTITY`, the recipient (i.e. a foreign key to ACL_SID), whether we'll be auditing or not, and the integer bit mask that represents the actual permission being granted or denied.