This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
rootdir_security [2022/02/11 13:09] yves [Accessing secured content] |
rootdir_security [2022/02/11 15:19] yves [Public vs private] |
||
---|---|---|---|
Line 47: | Line 47: | ||
If the credentials are faulty, an error appears | If the credentials are faulty, an error appears | ||
- | |||
=== S3 storage === | === S3 storage === | ||
+ | |||
+ | PMA.core is one of the few vendors that [[https://www.prweb.com/releases/pathomation_announces_support_for_cloud_storage_and_file_transfer_protocol_ftp_servers/prweb18296771.htm|supports cloud storage natively]]. | ||
+ | |||
+ | Let's say that you have an S3 bucket and put slides in it: | ||
+ | |||
+ | {{ ::rootdir_s3_10.png?direct&400 |}} | ||
+ | |||
+ | To protect access, you should create a dedicated entity that can only access that content. | ||
+ | |||
+ | {{ ::rootdir_s3_20.png?direct&400 |}} | ||
+ | |||
+ | You can then create a pair of dedicated access / secret keys for the new entity: | ||
+ | |||
+ | {{ :rootdir_s3_30.png?direct&400 |}} | ||
+ | |||
+ | These keys are then used to configure the S3 mounting point at the PMA.core side: | ||
+ | |||
+ | {{ :rootdir_s3_40.png?direct&400 |}} | ||
+ | |||
+ | The mounting point only functions when the provided credentials are still active on the S3 storage side. If not, an error message ensues: | ||
+ | |||
+ | {{ :rootdir_s3_50.png?direct&400 |}} | ||
+ | |||
+ | If all is well, you can now browse your slides directly from your S3 content. | ||
+ | |||
+ | {{ :rootdir_s3_60.png?direct&400 |}} | ||
=== Azure storage === | === 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 ==== | ==== 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 users and more root-directories, it becomes undesirable that everybody is allowed to see everything. |
Therefore, root-directories can be marked "public" or "private": | Therefore, root-directories can be marked "public" or "private": | ||
+ | |||
+ | {{ :rootdir_public_private_switch.png?direct&200 |}} | ||
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. | 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. |