Differences

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

--- misc [2022/02/14 15:01] – 84.198.201.169
+++ misc [2022/10/13 09:50] (current) – yves
@@ Line 3: / Line 3: @@
 ==== Advanced customization ====
-Depending on your license terms and specific installation, you may see more or less additional columns behind the login. E.g. you may have a restrictive version that doesn't allow you the granularity to determine which users may perform annotations and which ones may not. In that case the column 'Can Annotate' will not be visible for your particular installation. You should contact us if you feel absence of certain features is somehow an error, or if you think anything else is missing (that you were actually expecting to see).
+Depending on your license terms and specific installation, you may see more or less additional columns behind the login. E.g., you may have a restrictive version that doesn't allow you the granularity to determine which users may perform annotations and which ones may not. In that case, the column 'Can Annotate' will not be visible for your particular installation. You should [[https://www.pathomation.com/contact|contact us]] if you feel absence of certain features is somehow an error or if you think anything else is missing (that you were actually expecting to see).
 ==== Data encryption ====
@@ Line 10: / Line 10: @@
   * PMACORE_ENCRYPTION_KEY environment variable
-  * EncryptionKey key in the App_Data\Data\PMA.core.config file (fallback if no env var is defined)
+  * EncryptionKey key in the ''App_Data\Data\PMA.core.config'' file (fallback if no env var is defined)
-The choice of using an environment variable as a means to provide the encryption key was chosen as the second best alternative behind using specialized vaults, which are not applicable. The reasoning is that even if an attacker can read files in the file system where PMA.core is installed, they won't be able to read the encryption key, because it is not in a file.