Skip to content

Server

This manual lists all the configurations that the S-Filer Portal's Configuration CLI can change about the Server.

Configuration keyDescriptionDefault value
cfg.server.asynchronous.tasks.maximum.number.tasks.reserved.by.runner (Since 4.2.0)Maximum number of asynchronous tasks that will be reserved at any given time for each task runner (there is one runner for each concurrent task that can be executed).100
cfg.server.asynchronous.tasks.number.concurrent.tasks (Since 4.12.0)Number of asynchronous tasks that can be executed concurrently.10
cfg.server.asynchronous.tasks.pending.tasks.verification.frequency.seconds (Since 4.12.0)Frequency (in seconds) at which the server verifies if there are pending asynchronous tasks that can be executed.300
cfg.server.audit.service.report.include.automate.transfer (Since 2.1.0)Includes in the report the action done by S-Filer's extensionstrue
cfg.server.authentication.service.idle.valid.time.in.seconds (Since 3.0.3)This is the time in second that a logged user can spend without interacting with the system. This value is for S-Filer Server. This value is use for any Sfiler Server client, Gateway, command line interface etc... When this time is reach, the user will have to log again in the System to be able to use it.1800
cfg.server.certificate.expiration.job.certificate.expire.soon.delay (Since 4.13.0)Delay in days between the notification and the actual certificate expiration. Set to -1 to indicate that no notification should be sent. (Default: -1)-1
cfg.server.clickjacking.protection (Since 4.14.0)If you enable this property, S-Filer Portal Server will set values in the html header's metadata for X-Frame-Options and Content-Security-Policytrue
cfg.server.crypto.service.issuer (Since 3.0.3)Specifies the issuer of the cryptographic service.S-Filer
cfg.server.crypto.service.mfa.long.lived.token.valid.time.in.hours (Since 4.17.0)Defines the validity period for MFA long-lived tokens in hours.168
cfg.server.crypto.service.token.valid.time.in.seconds (Since 3.0.3)Specifies the validity period for cryptographic service tokens in seconds.86400
cfg.server.hsts.header.support (Since 4.14.0)This indicates whether HSTS headers should be added in Server responses. When it is active, browsers will only connect to pages on the same sub-domain in HTTPS. Activate this unless other pages served under the same sub-domain are unsecured (HTTP instead of HTTPS).true
cfg.server.hsts.header.support.max.age (Since 4.14.0)This indicates the time during which the browsers will remember to only use HTTPs for the Server responses (in seconds). Put in a small value at first such that if there is a mistake (or another site that is using HTTP and is not working), you can disable the HSTS and after some time, clients will be able to access the site in HTTP. If after initial deployment there are no errors, you can increase this value to a very long time.3600
cfg.server.ip (Since 4.1.4)Server host.
cfg.server.language.de (Since 4.3.0)Turn on the German languagetrue
cfg.server.language.en (Since 4.0.2)Turn on the English languagetrue
cfg.server.language.es (Since 4.0.8)Turn on the Spanish languagetrue
cfg.server.language.fr (Since 4.0.2)Turn on the French languagetrue
cfg.server.language.it (Since 4.14.0)Turn on the Italian languagetrue
cfg.server.logger.authentication.limited (Since 4.17.0)If set to "Yes", this configuration parameter will limit the verbosity of an authentication failure in the server logs.true
cfg.server.logger.level (Since 2.1.0)Log Level of S-Filer Server. When a problem occurs, the log file can be used to detect the problem cause. In normal operation, a Warning or Info Level is sufficient. When investigating a problem, use the Debug level to quickly and more deeply understand the cause. Leaving the Log level to DEBUG can decrease the system performance due to Disk access.INFO
cfg.server.mail.notification.service.from.address (Since 3.0.3)Sender email address of the email notification system.
cfg.server.mail.notification.service.from.name (Since 3.0.3)Name appearing as sender in email notification sent to users.S-Filer Notification System
cfg.server.mail.notification.service.reattempt.failed.notification.period.in.minutes (Since 3.0.3)Period of time (in minutes) during which the system will retry to send failed emails. After this period, the email is deleted without being sent. The frequency of the retries depends on the "Email Sender" schedule.2880
cfg.server.mail.notification.service.to.alert.address (Since 3.0.3)Address used when a scheduled event detects a problem with the system.
cfg.server.mail.notification.service.to.alert.language (Since 4.13.0)Language used when a scheduled event detects a problem with the system.en
cfg.server.mail.service.mail.auth.basic.enabled (Since 3.0.3)Determines whether to use or not the basic authentication with the email server.false
cfg.server.mail.service.mail.auth.basic.password (Since 3.0.3)Password used to access the email server.
cfg.server.mail.service.mail.auth.basic.user (Since 3.0.3)User name used to access the email server.
cfg.server.mail.service.mail.auth.oauth2.client.id (Since 4.18.0)This is the client identifier used to authenticate when retrieving an authentication token. For more details on this configuration, consult the SMTP OAuth2 article in the online documentation.
cfg.server.mail.service.mail.auth.oauth2.client.secret (Since 4.18.0)This is the client secret used to authenticate when retrieving an authentication token. For more details on this configuration, consult the SMTP OAuth2 article in the online documentation.
cfg.server.mail.service.mail.auth.oauth2.enabled (Since 4.18.0)Determines whether to use or not the OAuth2 authentication with the email server.false
cfg.server.mail.service.mail.auth.oauth2.scopes (Since 4.18.0)One or more scope values indicating to which resources access must be granted. For more details on this configuration, consult the SMTP OAuth2 article in the online documentation.
cfg.server.mail.service.mail.auth.oauth2.token.url (Since 4.18.0)This URL is used to retrieve the authentication token that is needed to use the email server. For more details on this configuration, consult the SMTP OAuth2 article in the online documentation.
cfg.server.mail.service.mail.auth.oauth2.user (Since 4.18.0)User name used to retrieve the authentication token. For more details on this configuration, consult the SMTP OAuth2 article in the online documentation.
cfg.server.mail.service.mail.host (Since 3.0.3)IP address or Hostname of the email server.
cfg.server.mail.service.mail.notification.body.extension (Since 3.0.3)Suffix of the files containing the body information._body.html
cfg.server.mail.service.mail.notification.path (Since 3.0.3)Path to text files used to create email notification.etc/mail/
cfg.server.mail.service.mail.notification.subject.extension (Since 3.0.3)File extension for files containing subject information._subject.html
cfg.server.mail.service.mail.port (Since 4.2.5)Port of the email server. Default: 25 (unsecure port), 465 (SSL port), 587 (STARTTLS port)25
cfg.server.mail.service.mail.protocol (Since 3.0.3)Protocol used to send Email.smtp
cfg.server.mail.service.mail.ssl (Since 4.2.5)Use a secure connection to the mail server.false
cfg.server.mail.service.mail.starttls (Since 4.2.5)Connect on an unsecure port and then ask the server to negotiate a secure connection to the mail server, often referred to as STARTTLS. Some servers (e.g. GMAIL) require both SSL and STARTTLS to work.false
cfg.server.mail.service.mail.theme.default (Since 4.1.0)The email notification "theme" that will be used to notify users for which no specific "theme" is specified.notification
cfg.server.mail.service.mail.timeout (Since 4.14.0)Number of milliseconds after which the S-Filer server will stop waiting for the email server if it has not responded.60000
cfg.server.management.service.anonymous.usergroup.bitwise (Since 3.0.3)This AND/OR value determines how "Quick Send" permissions from many groups are combined for a user. When set to AND, all groups must give the permission. When set to OR, at least one group must give the permission.OR
cfg.server.management.service.community.communityid.max.length (Since 3.0.3)Maximum length allowed for the Community IDs. Validated by S-Filer Server.128
cfg.server.management.service.community.description.max.length (Since 3.0.3)Maximum length allowed for the Community Description. Validated by S-Filer Server.128
cfg.server.management.service.delete.disabled.user.interval.days (Since 4.0.0)This value is the number of days that a disabled user will remain in the S-Filer system. After this number of days, the user will be deleted. If this value is less than or equal to 0, the system will not delete any disabled users.180
cfg.server.management.service.download.usergroup.bitwise (Since 3.0.3)This AND/OR value determines how "Download" permissions from many groups are combined for a user. When set to AND, all groups must give the permission. When set to OR, at least one group must give the permission.OR
cfg.server.management.service.inactive.user.max.days (Since 4.0.0)Sets the maximum number of days a user can be inactive before being marked inactive.180
cfg.server.management.service.ipvalidation.usergroup.bitwise (Since 3.0.3)This AND/OR value determines how IP address restrictions from many groups are combined for a user. When set to AND, all groups must allow the IP address. When set to OR, at least one group must allow the IP address.OR
cfg.server.management.service.upload.usergroup.bitwise (Since 3.0.3)This AND/OR value determines how "Upload" permissions from many groups are combined for a user. When set to AND, all groups must give the permission. When set to OR, at least one group must give the permission.OR
cfg.server.management.service.user.alias.max.length (Since 3.0.3)Maximum length allowed for user Folder Alias. Validated by S-Filer Server.128
cfg.server.management.service.user.email.max.length (Since 3.0.3)Maximum length allowed for user Email Address. Validated by S-Filer Server.128
cfg.server.management.service.user.fullname.max.length (Since 3.0.3)Maximum length allowed for user full name. Validated by S-Filer Server.128
cfg.server.management.service.user.username.max.length (Since 3.0.3)Maximum length allowed for Username. Validated by S-Filer Server.128
cfg.server.management.service.usergroup.description.max.length (Since 3.0.3)Maximum length allowed for Group Description. Validated by S-Filer Server.128
cfg.server.management.service.usergroup.groupid.max.length (Since 3.0.3)Maximum length allowed for Group IP field. Validated by S-Filer Server.128
cfg.server.port (Since 4.1.4)Server port
cfg.server.protocol (Since 4.1.4)HTTPS protocol can be used.
cfg.server.report.service.jasper.xml.source.audits (Since 3.0.3)Path to the Audit Transfer Report source file.report/AuditsReport.xml
cfg.server.report.service.jasper.xml.source.audits.csv (Since 3.0.3)Path to the Audit Transfer Report source file in CSV format.report/AuditsReport_csv.xml
cfg.server.report.service.jasper.xml.source.communities (Since 3.0.3)Path to the Community Report source file.report/CommunitiesReport.jrxml
cfg.server.report.service.jasper.xml.source.groups (Since 3.0.3)Path to the Group Report source file.report/GroupsReport.jrxml
cfg.server.report.service.jasper.xml.source.system.event.audits (Since 4.1.2)Path to the System Audit Report source file.report/SystemEventAuditsReport.xml
cfg.server.report.service.jasper.xml.source.system.event.audits.csv (Since 4.1.2)Path to the System Audit Report source file in CSV format.report/SystemEventAuditsReport_csv.xml
cfg.server.report.service.jasper.xml.source.users (Since 3.0.3)Path to the User Report source file.report/UsersReport.jrxml
cfg.server.report.service.report.include.automate.transfer (Since 3.0.3)Determines whether the report engine should include events from Extensions.true
cfg.server.report.service.report.logo (Since 3.0.3)Logo image file that will be displayed in the PDF report.etc/images/logo.jpg
cfg.server.rest.api.exposition.endpoint.assignGroupToCommunity (Since 4.15.0)Whether the assignGroupToCommunity REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.assignUserToCommunity (Since 4.15.0)Whether the assignUserToCommunity REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.assignUserToGroup (Since 4.15.0)Whether the assignUserToGroup REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.assignUserToShareByEmail (Since 4.17.0)Whether the assignUserToShareByEmail REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.assignUserToShareById (Since 4.17.0)Whether the assignUserToShareById REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.changePassword (Since 4.15.0)Whether the changePassword REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.completeTotpForUser (Since 4.15.0)Whether the completeTotpForUser REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.countTasks (Since 4.15.0)Whether the countTasks REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.createAccessTokenForUser (Since 4.15.0)Whether the createAccessTokenForUser REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.createCommunity (Since 4.15.0)Whether the createCommunity REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.createGroup (Since 4.15.0)Whether the createGroup REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.createNotificationTheme (Since 4.2.0)Whether the createNotificationTheme REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.createShare (Since 4.17.0)Whether the createShare REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.createTemplate (Since 4.18.0)Whether the createTemplate REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.createTotpForUser (Since 4.15.0)Whether the createTotpForUser REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.createUser (Since 4.15.0)Whether the createUser REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.delete (Since 4.15.0)Whether the delete REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.deleteAccessTokenForUser (Since 4.15.0)Whether the deleteAccessTokenForUser REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.deleteAccessTokensForUser (Since 4.15.0)Whether the deleteAccessTokensForUser REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.deleteCommunity (Since 4.15.0)Whether the deleteCommunity REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.deleteGroup (Since 4.15.0)Whether the deleteGroup REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.deleteNotificationTheme (Since 4.2.0)Whether the deleteNotificationTheme REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.deleteShare (Since 4.17.0)Whether the deleteShare REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.deleteTemplate (Since 4.18.0)Whether the deleteTemplate REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.deleteTotpForUser (Since 4.15.0)Whether the deleteTotpForUser REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.deleteTotpsForUser (Since 4.15.0)Whether the deleteTotpsForUser REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.deleteUser (Since 4.15.0)Whether the deleteUser REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.downloadFromFileVersionId (Since 4.15.0)Whether the downloadFromFileVersionId REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.downloadFromNodeId (Since 4.15.0)Whether the downloadFromNodeId REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.findAccessTokenForUser (Since 4.15.0)Whether the findAccessTokenForUser REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.findAccessTokensForUser (Since 4.15.0)Whether the findAccessTokensForUser REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.findCommunities (Since 4.15.0)Whether the findCommunities REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.findCommunitiesForGroup (Since 4.15.0)Whether the findCommunitiesForGroup REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.findCommunitiesForUser (Since 4.15.0)Whether the findCommunitiesForUser REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.findDomains (Since 4.15.0)Whether the findDomains REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.findGroups (Since 4.15.0)Whether the findGroups REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.findGroupsForCommunity (Since 4.15.0)Whether the findGroupsForCommunity REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.findGroupsForUser (Since 4.15.0)Whether the findGroupsForUser REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.findNotificationThemeContents (Since 4.2.0)Whether the findNotificationThemeContents REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.findNotificationThemes (Since 4.2.0)Whether the findNotificationThemes REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.findShareUsers (Since 4.17.0)Whether the findShareUsers REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.findStorages (Since 4.18.0)Whether the findStorages REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.findTemplates (Since 4.18.0)Whether the findTemplates REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.findTotpForUser (Since 4.15.0)Whether the findTotpForUser REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.findTotpsForUser (Since 4.15.0)Whether the findTotpsForUser REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.findUsers (Since 4.15.0)Whether the findUsers REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.findUsersForCommunity (Since 4.15.0)Whether the findUsersForCommunity REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.findUsersForGroup (Since 4.15.0)Whether the findUsersForGroup REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.getCommunity (Since 4.15.0)Whether the getCommunity REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.getFileInfoByNodeId (Since 4.15.0)Whether the getFileInfoByNodeId REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.getFileVersionByFileVersionId (Since 4.15.0)Whether the getFileVersionByFileVersionId REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.getGroup (Since 4.15.0)Whether the getGroup REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.getLicenseStats (Since 4.19.0)Whether the getLicenseStats REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.getNotificationTheme (Since 4.2.0)Whether the getNotificationTheme REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.getNotificationThemeContent (Since 4.2.0)Whether the getNotificationThemeContent REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.getShare (Since 4.17.0)Whether the getShare REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.getSystemCapabilities (Since 4.17.0)Whether the getSystemCapabilities REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.getTaskByUuid (Since 4.15.0)Whether the getTaskByUuid REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.getTemplate (Since 4.18.0)Whether the getTemplate REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.getTransferContextByUploadId (Since 4.15.0)Whether the getTransferContextByUploadId REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.getTransferStats (Since 4.15.0)Whether the getTransferStats REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.getUser (Since 4.15.0)Whether the getUser REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.list (Since 4.15.0)Whether the list REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.lockUser (Since 4.15.0)Whether the lockUser REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.login (Since 4.15.0)Whether the login REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.logout (Since 4.15.0)Whether the logout REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.mfaTotpValidateCode (Since 4.15.0)Whether the mfaTotpValidateCode REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.mfaValidateLongLivedToken (Since 4.17.0)Whether the mfaValidateLongLivedToken REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.mkdir (Since 4.15.0)Whether the mkdir REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.move (Since 4.15.0)Whether the move REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.queryUsersByRemainingSpace (Since 4.15.0)Whether the queryUsersByRemainingSpace REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.rename (Since 4.15.0)Whether the rename REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.resetUserPassword (Since 4.15.0)Whether the resetUserPassword REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.resolve (Since 4.15.0)Whether the resolve REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.takeShareOwnership (Since 4.17.0)Whether the takeShareOwnership REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.testNotification (Since 4.2.0)Whether the testNotification REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.transferShareOwnership (Since 4.17.0)Whether the transferShareOwnership REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.ttl (Since 4.15.0)Whether the ttl REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.unassignGroupFromCommunity (Since 4.15.0)Whether the unassignGroupFromCommunity REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.unassignUserFromCommunity (Since 4.15.0)Whether the unassignUserFromCommunity REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.unassignUserFromGroup (Since 4.15.0)Whether the unassignUserFromGroup REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.unassignUserFromShare (Since 4.17.0)Whether the unassignUserFromShare REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.unlockUser (Since 4.15.0)Whether the unlockUser REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.updateCommunity (Since 4.15.0)Whether the updateCommunity REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.updateGroup (Since 4.15.0)Whether the updateGroup REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.updateNotificationTheme (Since 4.2.0)Whether the updateNotificationTheme REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.updateNotificationThemeContent (Since 4.2.0)Whether the updateNotificationThemeContent REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.updateShare (Since 4.17.0)Whether the updateShare REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.updateTemplate (Since 4.18.0)Whether the updateTemplate REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.updateUser (Since 4.15.0)Whether the updateUser REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.updateUserRoleInShare (Since 4.17.0)Whether the updateUserRoleInShare REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.uploadAnonymousHttpFile (Since 4.15.0)Whether the uploadAnonymousHttpFile REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.uploadMembersHttpFile (Since 4.15.0)Whether the uploadMembersHttpFile REST API component is exposed.false
cfg.server.rest.api.exposition.endpoint.uploadNodeHttpFile (Since 4.15.0)Whether the uploadNodeHttpFile REST API component is exposed.false
cfg.server.rest.api.exposition.filter.active (Since 4.15.0)Indicates whether the REST API exposition filter is active.false
cfg.server.rest.api.exposition.override.description (Since 4.15.0)Provides an override for the default description in the REST API exposition.
cfg.server.rest.api.exposition.override.title (Since 4.15.0)Provides an override for the default title in the REST API exposition.
cfg.server.system.event.audit.alert.on.fail (Since 4.1.2)Send an email notification when the integrity check has failed. The email notification is sent to the address specified in the Email section.true
cfg.server.system.event.audit.days (Since 4.3.0)Audit will be kept for X number of days365
cfg.server.system.event.audit.keep (Since 4.3.0)If Yes entries will be archived to a file. If No, they will be deleted.false
cfg.server.system.event.audit.prefix (Since 4.3.0)Archives files will be prefixed with entered value.archive
cfg.server.system.event.audit.service.activate (Since 4.1.2)Activate the System Event Audit. Select "YES" to log the system events.true
cfg.server.system.event.audit.targetFolder (Since 4.3.0)Archives files will be written in this folder./
cfg.server.transfer.service.absolute.files.retention.period.in.days (Since 3.0.3)Maximum number of days that a file can be present in the server. Use a value equal to or less than 0 to specify an unlimited duration.730
cfg.server.transfer.service.anonymous.max.nb.downloads (Since 4.1.0)This is the default value for the number of downloads allowed for "Quick Send" transfers. A value below or equal to 0 will result in an unlimited number of downloads.1
cfg.server.transfer.service.community.allowed.inactivity.period (Since 4.17.0)Number of days a Community must be inactive before it is automatically deleted. The inactive Community cleanup will be disabled if this value is less than or equal to 0. Note that downloading or uploading a file in a Community resets its inactivity period and that a Community with an expiration date will never be deleted due to its inactivity period.-1
cfg.server.transfer.service.community.expiration.notification.days (Since 4.17.0)Notification email will be sent to the administrators of a Community that is within this number of days of being automatically deleted because of its expiration date or inactivity period. The email notification will be disabled if this value is less than or equal to 0.7
cfg.server.transfer.service.delete.expired.file.period (Since 4.1.0)Specify the number of minutes to wait before deleting expired files.120
cfg.server.transfer.service.encrypted.cek.retention.period.in.days (Since 3.0.3)Maximum number of days that a pending upload will be available for resume.7
cfg.server.transfer.service.files.inactivity.period.in.days (Since 3.0.3)Maximum number of days that an inactive file will stay on the system. Use a value equal to or less than 0 to specify an unlimited duration.365
cfg.server.transfer.service.files.retention.period.community.overrideable.enabled (Since 4.8.3)This option indicates whether a system administrator can exceed the absolute retention period when setting a community retention period. Usually, the absolute retention period can never be exceeded, but this allows an exception to this rule.false
cfg.server.transfer.service.mail.notification.absolute.files.retention.period.in.days (Since 3.0.3)Absolute maximum number days before sending a notice to owner.-1
cfg.server.transfer.service.mail.notification.files.retention.period.in.days (Since 3.0.3)Maximum number days before sending a notice to owner.-1
cfg.server.transfer.service.page.size.query (Since 3.0.3)During cleanup, this value determines how much data to manage at once.1000
cfg.server.transfer.service.rest.anonymous.download (Since 4.13.0)Whether to allow the REST API users to use the "Quick Send" feature. This feature enables sending files to a user using his email address.true
cfg.server.transfer.service.rest.http.allowed (Since 4.13.0)Whether to allow the REST API users to transfer files using HTTPS (without end-to-end encryption). Since end-to-end encryption is not supported by the REST API, all transfers will be forbidden if this feature is disabled.true
cfg.server.transfer.service.rest.share.enabled (Since 4.17.0)Whether to allow the REST API users to use the "Share file" feature. This feature enables users to create "shares" in which they can invite other users to participate using their email address.false
cfg.server.transfer.service.share.allowed.inactivity.period (Since 4.12.0)Number of days a Share must be inactive before it is automatically deleted. The inactive Share cleanup will be disabled if this value is less than or equal to 0. Note that downloading or uploading a file in a Share resets its inactivity period and that a Share with an expiration date will never be deleted due to its inactivity period.180
cfg.server.transfer.service.share.expiration.notification.days (Since 4.12.0)Notification email will be sent to the administrators of a Share that is within this number of days of being automatically deleted because of its expiration date or inactivity period. The email notification will be disabled if this value is less than or equal to 0.7
cfg.server.transfer.service.throttling.max.task.backlog (Since 4.13.0)S-Filer performs many tasks on background threads including the post-processing of files after transfers. This setting dictates the maximum backlog (in seconds) for tasks. When the backlog exceeds this value, transfers will be throttled by refusing some of them until the backlog drops below this threshold.30
cfg.server.webserver.service.jetty.receive.timeout (Since 2.1.0)Session timeout of the internal Jetty server.30000
cfg.server.webserver.service.jetty.server.private.key (Since 4.9.0)The key used to secure the HTTPS connection to the server.
cfg.server.webserver.service.jetty.server.ssl.cipher.management.mode (Since 4.6.1)Determines how SSL/TLS ciphers are managed. S-Filer maintains a list of strong ciphers that will evolve over time. The 'Automatic' mode allows to enable only the strong ciphers from this list. For some older clients, weaker ciphers may need to be enabled because they don't support any of the strong ones. The 'JVM Default' mode results in all ciphers present on the JVM to be enabled. For a more fine-grained control, the 'Custom' mode allows to specify all the ciphers that must be enabled in the 'Custom SSL/TLS ciphers' parameter.AUTOMATIC
cfg.server.webserver.service.jetty.server.ssl.custom.ciphers (Since 4.17.0)List of SSL/TLS ciphers (separated by comma) that will be enabled if the cipher management mode is 'Custom'. WARNING: Some ciphers specified in this list may not be available depending on the key type of the SSL/TLS private key.TLS_AES_128_GCM_SHA256,TLS_AES_256_GCM_SHA384,TLS_CHACHA20_POLY1305_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256,TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_DHE_RSA_WITH_AES_256_GCM_SHA384,TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
cfg.server.webserver.service.jetty.server.ssl.sni.host.check (Since 4.19.0)Determines if the SSL/TLS SNI host check is enabled. SNI (Server Name Indication) is an extension to the SSL/TLS protocol by which a client indicates which hostname it is attempting to connect to at the start of the connection process. If the SNI host check is enabled and the hostname of the server to which the client is trying to connect to is not found in the server certificate, the server returns an invalid SNI error.true