|
|
|
Security |
|
|
|
|
|
|
Security |
|
|
|
|
Security
|
|
|
Security |
|
|
|
|
|
|
Security |
|
|
|
|
This dialog is divided into two independent sections - Permissions and Access.
Permissions
Here you can specify the document-level permissions for the given document. Please see Developer's Guide -> Development -> Membership, permissions and security -> Permissions for more details.
|
Document-level and global permissions
Please remember that the document level permissions defined on this tab are combined with global permissions defined for roles in the CMS Desk -> Administration -> Permissions dialog as described in the Developer's Guide -> Development -> Membership, permissions and security -> Permissions chapter.
|
Breaking and restoring permission inheritance
In case you need to break the permission inheritance and configure different permissions for some site section, you need to click Change permission inheritance... link in the Security dialog and choose one of the following options:
| • | Break inheritance and copy parent permissions - breaks inheritance and adds parent permissions to the document, while original permissions configured for the document are preserved. |
| • | Break inheritance and remove parent permissions - breaks inheritance and removes all permissions inherited from the parent, while additional permissions configured for the document are preserved. |
If you decide to inherit the permissions from the parent again, click the Change permission inheritance... link on the Security tab. Two options will be offered:
| • | Restore inheritance to parent document permissions (current document only) - makes the current document inherit permissions of the parent document. |
| • | Recursively restore inheritance to parent document permissions (current and all child documents) - makes the current document and all its child documents inherit permissions of the parent document, while only documents which do not inherit parent permissions are affected by this action. |
Access
In this section, the following two options are available:
Requires authentication:
| • | Yes - authentication is required to access the page. |
| • | No - authentication is not required to access the page. |
| • | Inherits - value of the setting is required from the parent page. |
Requires SSL:
This setting indicates if users who access the page should automatically be redirected to the version of the page that is secured through the SSL protocol (i.e. the target URL will use the https scheme). You can choose one of the following options:
| • | Yes - users attempting to access the page will always be redirected to the HTTPS version of the page's URL. |
| • | No - users will not be explicitly redirected to a secured URL when they access the page, but the protocol used in the current URL will remain unchanged (i.e. if a user navigates to the page from another page that is secured, this page will also use SSL). |
| • | Inherits - the settings defined for the parent document will be used. |
| • | Never - users trying to access the page through a secured URL will be explicitly redirected to the unsecured version of the page. |
Please note: Kentico CMS does not configure your website for SSL/HTTPS. It may only be used to automatically redirect users to the appropriate URL. You need to perform the configuration itself manually using the standard IIS settings, as described in IIS documentation or in this article: http://msdn.microsoft.com/cs-cz/magazine/cc301946(en-us).aspx
