CKFinder 1.x/Developers Guide/ColdFusion/Configuration/Access Control - Revision history

Admin: moved CKFinder/Developers Guide/ColdFusion/Configuration/Access Control to CKFinder 1.x/Developers Guide/ColdFusion/Configuration/Access Control

2010-05-28T06:46:32Z

moved CKFinder/Developers Guide/ColdFusion/Configuration/Access Control to CKFinder 1.x/Developers Guide/ColdFusion/Configuration/Access Control

Wiktor: /* Example 1 */

2009-03-12T10:02:32Z

‎Example 1

Wiktor: /* Example 2 */

2009-03-12T09:50:31Z

‎Example 2

Wiktor: /* Example 1 */

2009-03-12T09:50:13Z

‎Example 1

Wiktor at 09:49, 12 March 2009

2009-03-12T09:49:37Z

Show changes

Wiktor: Reverted edits by Wiktor (Talk); changed back to last version by W.olchawa

2009-03-12T09:46:47Z

Reverted edits by Wiktor (Talk); changed back to last version by W.olchawa

Show changes

Wiktor: /* Example 2 */

2009-03-12T09:46:14Z

‎Example 2

Wiktor: /* The syntax of the ACL Items */

2009-03-12T09:45:31Z

‎The syntax of the ACL Items

Wiktor: /* Example 2 */

2009-03-12T09:45:14Z

‎Example 2

Wiktor: /* Example 1 */

2009-03-12T09:44:21Z

‎Example 1

@@ Line 39: / Line 39: @@
 config.accessControl[2].fileDelete = false;
 </pre>
-The above example only refers to file operations in the folder '/Logos' itself. It doesn't restrict operations on the folder so the user can delete or rename the folder. In order to limit users ability to modify the folder (not its context) you should change permissions in the parent folder.
+The above example only refers to file operations in the folder '/Logos' itself. It doesn't restrict operations on the folder so the user can delete or rename the folder. In order to limit users ability to modify the folder (not its contents) you should change permissions in the parent folder.
 ==== Example 2 ====

@@ Line 42: / Line 42: @@
 ==== Example 2 ====
-<pre>config.accessControl[2] = structNew();
+<pre>config.accessControl[3] = structNew();
-config.accessControl[2].role = '*';
+config.accessControl[3].role = '*';
-config.accessControl[2].resourceType = 'Images';
+config.accessControl[3].resourceType = 'Images';
-config.accessControl[2].folder = '/';
+config.accessControl[3].folder = '/';
-config.accessControl[2].folderView = true;
+config.accessControl[3].folderView = true;
-config.accessControl[2].folderCreate = true;
+config.accessControl[3].folderCreate = true;
-config.accessControl[2].folderRename = false;
+config.accessControl[3].folderRename = false;
-config.accessControl[2].folderDelete = false;
+config.accessControl[3].folderDelete = false;
-config.accessControl[2].fileView = true;
+config.accessControl[3].fileView = true;
-config.accessControl[2].fileUpload = true;
+config.accessControl[3].fileUpload = true;
-config.accessControl[2].fileRename = true;
+config.accessControl[3].fileRename = true;
-config.accessControl[2].fileDelete = true;
+config.accessControl[3].fileDelete = true;
 </pre>
 Now a user can view and create a folder, but he will be unable to rename or delete it.&nbsp;<br>

@@ Line 24: / Line 24: @@
 If you want to restrict the upload, rename or delete of files in the "Logos" folder of the resource type "Images":
 <pre>
-config.accessControl[3] = structNew();
+config.accessControl[2] = structNew();
-config.accessControl[3].role = '*';
+config.accessControl[2].role = '*';
-config.accessControl[3].resourceType = 'Images';
+config.accessControl[2].resourceType = 'Images';
-config.accessControl[3].folder = '/Logos';
+config.accessControl[2].folder = '/Logos';
-config.accessControl[3].folderView = true;
+config.accessControl[2].folderView = true;
-config.accessControl[3].folderCreate = true;
+config.accessControl[2].folderCreate = true;
-config.accessControl[3].folderRename = true;
+config.accessControl[2].folderRename = true;
-config.accessControl[3].folderDelete = true;
+config.accessControl[2].folderDelete = true;
-config.accessControl[3].fileView = true;
+config.accessControl[2].fileView = true;
-config.accessControl[3].fileUpload = false;
+config.accessControl[2].fileUpload = false;
-config.accessControl[3].fileRename = false;
+config.accessControl[2].fileRename = false;
-config.accessControl[3].fileDelete = false;
+config.accessControl[2].fileDelete = false;
 </pre>
 The above example only refers to file operations in the folder '/Logos' itself. It doesn't restrict operations on the folder so the user can delete or rename the folder. In order to limit users ability to modify the folder (not its context) you should change permissions in the parent folder.

@@ Line 42: / Line 42: @@
 ==== Example 2 ====
-<pre>config.accessControl[3] = structNew();
+<pre>config.accessControl[2] = structNew();
-config.accessControl[3].role = '*';
+config.accessControl[2].role = '*';
-config.accessControl[3].resourceType = 'Images';
+config.accessControl[2].resourceType = 'Images';
-config.accessControl[3].folder = '/';
+config.accessControl[2].folder = '/';
-config.accessControl[3].folderView = true;
+config.accessControl[2].folderView = true;
-config.accessControl[3].folderCreate = true;
+config.accessControl[2].folderCreate = true;
-config.accessControl[3].folderRename = false;
+config.accessControl[2].folderRename = false;
-config.accessControl[3].folderDelete = false;
+config.accessControl[2].folderDelete = false;
-config.accessControl[3].fileView = true;
+config.accessControl[2].fileView = true;
-config.accessControl[3].fileUpload = true;
+config.accessControl[2].fileUpload = true;
-config.accessControl[3].fileRename = true;
+config.accessControl[2].fileRename = true;
-config.accessControl[3].fileDelete = true;
+config.accessControl[2].fileDelete = true;
 </pre>
 Now a user can view and create a folder, but he will be unable to rename or delete it.&nbsp;<br>

@@ Line 8: / Line 8: @@
 config.accessControl[1].resourceType = '*';
 config.accessControl[1].folder = '/';
 config.accessControl[1].folderView = true;
 config.accessControl[1].folderCreate = true;
 config.accessControl[1].folderRename = true;
 config.accessControl[1].folderDelete = true;
 config.accessControl[1].fileView = true;
 config.accessControl[1].fileUpload = true;

← Older revision	Revision as of 06:46, 28 May 2010
(No difference)