 |
Xentara v2.0.1
User Manual
|
|
Xentara v2.0.1
User Manual
|
Under Linux, the Xentara application is called xentara and is located under /usr/bin. xentara accepts the following command line options:
--help
Shows help for the Xentara command line options and exits.
--version
Outputs version information for Xentara and exits.
--config-dir=<path> or --config-dir <path>
Specifies an additional directory to search for configuration files before the standard locations are searched. <path> must be the path to the configuration directory. These directories are not searched for any files whose path has been specified using --model, --config, --security, --oauth2, --client-certs, --users, or --passwords.
This option can be specified multiple times.
--model=<path> or --model <path>
Specifies the model file to use. <path> must be the path to the model file. If you do not specify a model file, the file will be searched for in a number of standard locations.
--config=<path> or --config <path>
Specifies the config file to use. <path> must be the path to the config file. If you do not specify a config file, the file will be searched for in a number of standard locations. If no config file is found, the default configuration will be used.
--security=<path> or --security <path>
Specifies the security configuration file to use. <path> must be the path to the security configuration file. If you do not specify a security configuration file, the file will be searched for in a number of standard locations. If no security configuration file is found, the default security configuration will be used.
--oauth2=<path> or --oauth2 <path>
Specifies the OAuth 2.0 configuration file to use. <path> must be the path to the OAuth 2.0 configuration file. If you do not specify an OAuth 2.0 configuration file, the file will be searched for in a number of standard locations. If no OAuth 2.0 configuration file is found, authorization of remote clients via OAuth 2.0 will not be possible.
--client-certs=<path> or --client-certs <path>
Specifies the client certificate configuration file to use. <path> must be the path to the client certificate configuration file. If you do not specify a client certificate configuration file, the file will be searched for in a number of standard locations. If no client certificate configuration file is found, authentication of remote clients via certificate-based authentication will not be possible.
--users=<path> or --users <path>
Specifies the user configuration file to use. <path> must be the path to the user configuration file. If you do not specify a user configuration file, the file will be searched for in a number of standard locations. If no user configuration file is found, authentication of remote clients via user username/password authentication will not be possible.
--passwords=<path> or --passwords <path>
Specifies the password file to use. <path> must be the path to the password file. If you do not specify a password file, the file will be searched for in a number of standard locations. If no password file is found, none of the users will have passwords, and authentication of remote clients via user username/password authentication will not be possible.
--plugin=<path> or --plugin <path>
Specifies an additional single plugin manifest. <path> must be the path to the manifest file.
This option can be specified multiple times.
--plugin-dir=<path> or --plugin-dir <path>
Specifies an additional directory for the plugin manifest search path. <path> must be the path to the directory containing the extra plugin manifests.
This option can be specified multiple times.
Under Windows, the Xentara application is called Xentara.exe and is located under App in the installation directory. Xentara.exe accepts the following command line options:
-Help or /?
Shows help for the Xentara command line options and exits.
-Version
Outputs version information for Xentara and exits.
Specifies an additional directory to search for configuration files before the standard locations are searched. <path> must be the path to the configuration directory. These directories are not searched for any files whose path has been specified using -Model, -Config, -Security, -OAuth2, -ClientCerts, -Users, or -Passwords.
This option can be specified multiple times.
Specifies the model file to use. <path> must be the path to the model file. If you do not specify a model file, the file will be searched for in a number of standard locations.
-Config <path>
Specifies the config file to use. <path> must be the path to the config file. If you do not specify a config file, the file will be searched for in a number of standard locations. If no config file is found, the default configuration will be used.
-Security <path>
Specifies the security configuration file to use. <path> must be the path to the security config file. If you do not specify a config file, the file will be searched for in a number of standard locations. If no security config file is found, the default security configuration will be used.
-OAuth2 <path>
Specifies the OAuth 2.0 configuration file to use. <path> must be the path to the OAuth 2.0 configuration file. If you do not specify an OAuth 2.0 configuration file, the file will be searched for in a number of standard locations. If no OAuth 2.0 configuration file is found, authorization of remote clients via OAuth 2.0 will not be possible.
-ClientCerts <path>
Specifies the client certificate configuration file to use. <path> must be the path to the client certificate configuration file. If you do not specify a client certificate configuration file, the file will be searched for in a number of standard locations. If no client certificate configuration file is found, authentication of remote clients via certificate-based authentication will not be possible.
-Users <path>
Specifies the user configuration file to use. <path> must be the path to the user configuration file. If you do not specify a user configuration file, the file will be searched for in a number of standard locations. If no user configuration file is found, authentication of remote clients via user username/password authentication will not be possible.
-Passwords <path>
Specifies the password file to use. <path> must be the path to the password file. If you do not specify a password file, the file will be searched for in a number of standard locations. If no password file is found, none of the users will have passwords, and authentication of remote clients via user username/password authentication will not be possible.
-Plugin <path>
Specifies an additional single plugin manifest. <path> must be the path to the manifest file.
This option can be specified multiple times.
-PluginDir <path>
Specifies an additional directory for the plugin manifest search path. <path> must be the path to the directory containing the extra plugin manifests.
This option can be specified multiple times.