export-config

Allows you to export a configuration file for one of the two components of S-Filer Portal: Gateway or GUI.

Syntax:

sfiler-cli [options] export-config [command options]

Command options	Required / Optional	Description
-n	Required	Instance name (e.g. my-gateway)
-ccf	Optional	The Component Configuration File where the configuration will be saved. If not provided, the file will be saved in the current folder using the default configuration file name (sfiler.conf for the Gateway and gui.conf for the GUI).

Example:

Linux

./sfiler-config-cli.sh -l my-user -p my-password -cf "conf/sfiler.conf" export-config -n my-gateway -ccf ./conf/sfiler.conf

Windows

.\sfiler-config-cli.bat -l my-user -p my-password -cf "conf\sfiler.conf" export-config -n my-gateway -ccf ./conf/sfiler.conf

Execution of this command will create a file in the /conf directory with the name sfiler.conf. The file must then be moved to the configuration directory of the component concerned (Gateway in this example) in order to be used. There's no need to modify the contents of the file produced by the command; it's ready to be used as is.

This command may return an error similar to:

PKCS information is not available for the component: My Gateway

If this situation occurs, it means that the Pkcs12 and Pkcs12Password fields in the Instance table of the database are not filled. It is important that these fields are filled for this command to work properly. You must therefore renew the keys to fix the problem. You can renew the keys using the renew-key command of sfiler-config-cli, or by using the administration console web interface. Once the PKCS12 information is present in the database, you can export the configuration.

NOTE

This command replaces the export-basic-config command used in previous versions (< 4.19.0) of S-Filer Portal.