| At line 3 changed one line |
| Max simultaneous logins controls how many times this username can be logged in at once. |
| Expire password will force the user to change their password every X number of days. |
| At line 5 added 2 lines |
| Max simultaneous logins controls how many times this username can be logged in at once. Be extremely careful setting this to a restrictive value as clients will have trouble connecting. For instance, web browsers often need at least 8. |
|
| At line 17 added 2 lines |
| Allow receiving shared items from other users is an enterprise sonly feature. The WebInterface allows sharing between multiple users and this will allow a user to receive these items, or ignore them. |
|
| At line 17 changed one line |
| The protocols the user can use determines if they are allowed to use insecure protocols for example, or maybe you want to block them using WebDAV. |
| The protocols the user can use determines if they are allowed to use insecure protocols for example, or maybe you want to block them using WebDAV. You can also set the max logins per protocol. |
| At line 23 changed one line |
| The list of paths to trusted SSH key files controls the public / private key authentication that SFTP allows for. This setting does not want you to enter in a 'trusted keys file', or a folder path, but rather the path to the actual key file itself. So '/files/keys/' is not OK, while '/files/keys/ben.pub' would be OK. Separate multiple items with new lines. Most SSH key formats are supported. There is also a more generic way to use this field. If the key file has the exact name of the user logging in, you can instead reference the directory '/files/keys/'. In this case there would need ot be a file named 'ben' in that directory. |
| [SSH public key authentication|UserManagerRestrictionsSSH] can be configured here too. |
| At line 25 removed one line |
| [attachments|ssh_keys.png] |
| At line 27 changed one line |
| The Keystore location, password, and key pass are used in FTPS proxy connections, or when requiring a valid client certificate from a HTTPS or FTPS connection. Client certificates are not used very frequently, so if you are unsure of what it is, dont' enable it or no one will be able to connect. |
| File based encryption can be enabled so that all files uploaded into this account are written to disk with PGP encryption. Here you can generate and configure the PGP key. Use this feature with caution so you don't accidentally loose the PGP key and make the data useless... Files uploaded will also be decrypted on the fly making this seamless data at rest encryption. |
| At line 29 changed one line |
| [attachments|ssl_certs.png] |
| [attachments|file_encryption.png] |