Differences

This shows you the differences between two versions of the page.

--- rootdir_security [2022/02/11 15:00]
yves
+++ rootdir_security [2022/08/06 19:28]
yves
@@ Line 7: / Line 7: @@
       * Configure public/secret key combinations for S3 resources
       * Configure account credentials to be used when accessing a UNC network resource path
-  * Prevent users from access mounted content through root directories that they are or are not allowed to do
+  * Prevent [[user_management|users]] from access mounted content through root directories that they are or are not allowed to do
       * Define Access control lists
@@ Line 16: / Line 16: @@
 Based on the type of data storage that a root directory's mounting point refers to, the configuration offers different options:
-=== Local hard disk entry points ===
+  * [[rootdir_local|Local hard disk entry points]]
 If you want to expose a local folder on the server's hard disk as a root directory in PMA.core, you have to give the IIS user account access rights to the folder using the Windows Explorer:
@@ Line 76: / Line 76: @@
 {{ :rootdir_s3_60.png?direct&400 |}}
+As of version 3.1, PMA.core also supports IAM AWS Role policies.
 === Azure storage ===
+Microsoft Azure has its own protocol, and so we provide a separate mounting point type of it.
+Let's say that you have an Azure container defined and put some slides in it already:
+{{ :rootdir_azure_10.png?direct&400 |}}
+You can convert these credentials in a connectionstring:
+''%%DefaultEndpointsProtocol=https;AccountName=pathomation;AccountKey=SUPERSECRET;BlobEndpoint=https://pathomation.blob.core.windows.net/;QueueEndpoint=https://pathomation.queue.core.windows.net/;TableEndpoint=https://pathomation.table.core.windows.net/;FileEndpoint=https://pathomation.file.core.windows.net/;%%''
+This text snippet is then pasted in the connection string field of the mounting point properties:
+{{ :rootdir_azure_20.png?direct&400 |}}
+If all goes well, you can now serve your slides from your Azure storage repositories.
 ==== Public vs private ====
-As you have more users and more root-directories, it becomes undesirable that everybody is allow to see everything.
+As you have more [[user_management|users]] and more root-directories, it becomes undesirable that everybody is allowed to see everything.
 Therefore, root-directories can be marked "public" or "private":
-Public root directories are marked "public", it means every user has access to them. They can be accessed by anybody who is a registered user in the PMA.core user repository.
+{{ :rootdir_public_private_switch.png?direct&200 |}}
-Private root directories are marked "private", it means only select users can see the content. They are only accessible by those who have been explicitly given access to be allowed to access the folder through the directory's [[acl|access control list]].
+Public root directories are marked "public", it means every user has access to them. They can be accessed by anybody who is a registered user in [[user_management|the PMA.core user repository]].
+Private root directories are marked "private", it means only select users can see the content. They are only accessible by those who have been explicitly given access to be allowed to access the folder through the directory's [[rootdir_security#access_control_list|access control list]].
 ==== Access control lists ====
@@ Line 95: / Line 113: @@
 {{ :acl.png?nolink&400 |}}
+An interactive overview grid is available via the Root directories management view:
+{{ :rootdir_acl_20.png?direct&400 |}}
+As you get even more root-directories and more users, it is useful to get an overview of who has access to what. For that, you can request the ACL report from the root-directories view.
+{{ :overview.png?nolink&400 |}}
+The resulting report looks like this:
+{{ :overview2.png?nolink&400 |}}

PMA.core 3.0.1

User Tools

Site Tools

Differences

Page Tools