Sample Website Configuration File

  • Published on Jul 7, 2025
  • 1 minute(s) read
Prev Next

The configuration file for the sample website is named controller.properties. This file is typically located in:

web_root/OASSampleSite-sdk_version/WEB‑INF/classes/

The controller.properties file is a standard Java properties file, i.e. a key/value association text file.

Each component (authentication and signature) requires the same configuration data, consisting of:

  • OneSpan Authentication Server primary server SOAP end point (URL, mandatory)
  • OneSpan Authentication Server backup server SOAP end point (URL, optional)
  • Name of the OneSpan Authentication Server component to be used (plain text, mandatory)
  • Password format used by SOAP requests (mandatory, integer enum values)

Here is an example of a configuration file:

soap.host.primary = https://<authentication_server_ip>:8888
soap.host.backup = https://<authentication_server_ip>:8888
# Component type definitions
component.type.authentication = Authentication Sample Client
component.type.emvcap_authentication = Authentication Sample Client
component.type.signature = Signature Sample Client
component.type.provisioning.dp4mobile = DP4Mobile Provisioning Sample Client
component.type.provisioning.mdl = Multi-Device Licensing Provisioning Sample Client
component.type.signature.secure_channel = Signature Secure Channel Sample Client
component.type.authentication.secure_channel = Authentication with Secure Channel Sample Client
# valid values are : 4 (Cleartext/separate) or 0 (Cleartext/combined)
password.format = 0

After changing the Java properties file, restart the Apache Tomcat service.