Changes between Version 95 and Version 96 of S3/S3AAA

Timestamp:

09/10/12 17:39:57 (12 years ago)

Author:

Dominic König

Comment:

--

S3/S3AAA

@@ -135 +135 @@
 A user is considered the ''owner'' of a record if they are either the individual owner of the record (user ID == {{{owned_by_user}}}), '''or''' they are a member of the owner group ({{{owned_by_group}}}).
 
-If a record has '''no owner''', i.e. if both {{{owned_by_user}}} and {{{owned_by_role}}} are '''None''', then all authenticated users are considered the owner of this record (public record).
-
 In tables which do not define either of these meta-fields, ownership rules are not applied ({{{uacl}}} only).
 
@@ -143 +141 @@
   '''NOTE:''' the {{{owned_by_entity}}} field associates the record with a realm (see [#OrgAuth]) - it has ''no'' relevance for the ownership of the record by an individual user.
 
+  '''NOTE:''' If a record has '''no owner''', i.e. if both {{{owned_by_user}}} and {{{owned_by_role}}} are '''None''', then all authenticated users are considered the owner of this record (public record). As a consequence of that, any owner ACLs for the AUTHENTICATED-role would always include all records without owner - regardless of which realm they belong to.
+
+   ''Future versions could implement a deployment option to apply ownership more strictly and consider records without owner as not owned by any user (rather than as owned by all users).''
 ==== Session-Ownership  ====
 For anonymous users we can make the session own the records, so that a user can edit records they've just created, or read their cached feature queries.