OneSpan Web Configuration Tool (admintool)

OneSpan Web Configuration Tool requires administrative privileges to modify the Administration Web Interface configuration. Hence you need to run the command using an administrative account, e.g. Administrator if using Windows or root if using Linux, respectively.

Any changes made with the OneSpan Web Configuration Tool will not take effect until you restart the web application server, e.g. Apache Tomcat.

On Windows, the OneSpan Web Configuration Tool is launched using a batch file, i.e. %PROGRAMFILES%\VASCO\IAS Web Administration\admintool.bat. On Linux, the OneSpan Web Configuration Tool is launched using a shell script, i.e. /opt/vasco/iaswas/admintool.sh.

The script executes a Java executable file (admintool.jar) using an embedded Java Runtime Environment, which is included when the Administration Web Interface is installed using the Web Administration ServiceSetup.

You need to use the Java executable directly only if you want to deploy the Administration Web Interface web application manually to an existing web server instead of using the embedded Apache Tomcat installed with Web Administration Service (advanced installation).

OneSpan Web Configuration Tool uses a properties file (admintool.properties) stored along the Java executable file to save its configuration settings.

If you are using the Java executable directly, you need to specify the properties file by using one of the following methods:

• Specifying the system property com.vasco.identikey.webapps.configfile by using the Java Runtime Environment -D option, i.e.:

  java -Dcom.vasco.identikey.webapps.configfile=properties_file -jar admintool.jar ...

  In this case, you need to specify the -D option each time you run the OneSpan Web Configuration Tool Java executable and set it to the properties file including the absolute file path.

• Adding the properties file path to the classpath.

The keystore (keystore.jks) and trust store (truststore.jks) files are automatically created in the folder where the OneSpan Web Configuration Tool is located. The keystore is only created when client verification is set up.

For more information, see Setting up client certificate verification.