Update server configuration files

SecureTransport stores the following server configuration files in the database:

  • brules.xml
  • FileServicesInterfaceRegistry.xml
  • mime.types
  • sentinel-returncode-translation.xml
  • ssl.csr.conf
  • SSO Configuration Files - The Single Sign-On (SSO) related configuration files. For more information, refer to Single Sign-On (SSO) and Single Logout (SLO).

You can use the Server Configuration Files page to make changes on your local computer to the files listed, save the changes to the database, propagate the changes to all servers in a cluster, and configure SSO for end-users and administrators. For information about how to configure the SSO functionality in SecureTransport, refer to Single Sign-On (SSO) and Single Logout (SLO).

  1. On the Server Configuration page, select Configuration Files.
  2. The Server Configuration Files page is displayed.
  3. Download the file to update. (For example, right-click the file name link in your browser and selected Save Link As or Save Target As.)
  4. Update the file using a editor on your local computer.
  5. Click Browse and select the file or type the path to the file in the Selected File column.
  6. When you have completed updating one or more files, select the files to upload in the first column.
  7. Click Upload.
  8. SecureTransport uploads the selected files to the server and copies the files to all the other servers in the cluster. The servers load the updated configuration immediately.


  • SSO configuration files are replicated on Enterprise Clusters and Standard Clusters after they are uploaded in ZIP format.
  • Alternately, you can edit these configuration files on the server and then click Synchronize on the Server Configuration Files page for that server. The server saves the file in the database and copies the files to all the other servers in the cluster, and the servers load the updated configuration immediately.
  • For SSO configuration files, the Synchronize button will update the SSO-related configuration files in <FILEDRIVEHOME/conf/sso> directory with the database. This will only affect the current node.
  • Only ZIP format is accepted for SSO configuration files import.
  • Do not put the configuration files in a sub-directory inside the ZIP file.
  • You can list all SSO-related configuration files, by clicking on the Plus () icon. You can hide the same files, by clicking the Minus () icon.
  • You can download a single SSO-related configuration file, by clicking on the name of the file. You can also download all SSO files in ZIP format, by clicking on the SSO Configuration Files link.
  • When importing SSO Configuration Files on a SecureTransport Edge, make sure that the ZIP file contains the sso-admin.xml, otherwise the import will not be successful.
  • When importing the SSO Configuration Files in a Standard Cluster, make sure that the Transaction Manager service is running on the current node. For more information about Standard Cluster synchronization, Standard Cluster synchronization.

Related topics:

Related Links