Skip to content

Commit a0cdc4a

Browse files
[irods/irods_7985] Remove documentation on modifying StrictACLs
The server is now always using strict mode.
1 parent 2189bb5 commit a0cdc4a

File tree

1 file changed

+0
-23
lines changed

1 file changed

+0
-23
lines changed

docs/system_overview/users_and_permissions.md

Lines changed: 0 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -12,29 +12,6 @@ Inheritance is a collection-specific setting that determines the permission sett
1212

1313
Inheritance is especially useful when working with shared projects such as a public Collection to which all users should have read access. With Inheritance set to Enabled, any sub-Collections created under the public Collection will inherit the properties of the public Collection. Therefore, a user with read access to the public Collection will also have read access to all Data Objects and Collections created in the public Collection.
1414

15-
## StrictACL
16-
17-
The iRODS setting 'StrictACL' is configured on by default in iRODS. This setting can be found in the `/etc/irods/core.re` file under acAclPolicy{}.
18-
19-
The default setting is:
20-
21-
~~~
22-
acAclPolicy {msiAclPolicy("STRICT");}
23-
~~~
24-
25-
To set no policy, change the setting to:
26-
27-
~~~
28-
acAclPolicy {}
29-
~~~
30-
31-
or more explicitly:
32-
33-
~~~
34-
acAclPolicy {msiAclPolicy("REGULAR");}
35-
~~~
36-
37-
3815
## Tickets (Guest Access)
3916

4017
Users are able to create tickets and associate them (one to one) with a Data Object or Collection. These are either system-generated 15-character pseudo-random strings, composed of upper and lower case characters 'A-Z' and '0-9'; or optionally specified by the user creating the ticket.

0 commit comments

Comments
 (0)