Configuration This section covers several configurations tasks for your Faspex 5 application. Configuring transfer optionsBy default, Faspex uses the transfer settings from the Aspera Central Server section. Select Override default settings to set user-specific transfer settings, which take precedence over the server-wide settings.Configuring the web serverConfiguring email notificationsNotify users about various Faspex events, such as resetting a password, receiving a package, and so on.Configuring API clientsFaspex requires your application use OAuth 2 to authorize your application to access protected Faspex resources.Setting custom portsSetting up custom ports in Faspex 5 involves configuring unique communication channels to facilitate the transfer of data.Enabling file processingWhen file processing is enabled Faspex puts packages into a transient state (the UI shows files as uploaded for file processing) and waits for a third-party application (including IBM Aspera otfv-validator, IBM Aspera Orchestrator, or any other application that can integrate with Faspex 5 API) to successfully process all the files; if file processing on a package fails for one or more files, Faspex will not deliver the package. File processing occurs simultaneously with file uploads to ensure efficient data management.Configuring package processing webhooksAdmins can create one or more webhooks to notify external systems (using a POST call) when a package is uploaded. For example, a webhook request can initiate an IBM Aspera Orchestrator workflow. Configure filters to execute the applicable webhook for each uploaded package. Faspex does not process to any response to the POST request. OTFV-ValidatorOTFV is a Golang service that works as a file validator. It processes files to verify and validate their content. Examples of this could include virus scanning, file name checking or package names.Parent topic: Admin