The SOAP provisioning wrapper full-sdk maps all commands defined in the OneSpan Authentication Server provisioning WSDL file in a class called ProvisioningBean.
The provisioning commands return a ProvisioningCommandResponse object that wraps the server’s response. For a list of different methods defined by this class, see Overview of SOAP wrappers.
SOAP provisioning bean
The provisioning bean is configured through a standard Java properties file (flat text key/value association). If the file is not found, or some keys are missing in the file, hard-coded default values will be loaded.
Table: Provisioning bean configuration keys | |
Key name | Description |
|---|---|
soap.host.primary | The location of the primary OneSpan Authentication Server instance. Specified as the complete SOAP endpoint URL, including protocol and port number. Default value: https://localhost:8888 |
soap.host.backup | The location of the backup OneSpan Authentication Server instance. Specified as the complete SOAP endpoint URL, including protocol and port number. Default value: https://localhost:8888 |
component.type | The name of the OneSpan Authentication Server component used to handle the sample authentication requests on the server side. Default value: DP4Web Sample Provisioning Client |
password.format | The format of the password parameter. Possible values:
Default value: 4 (cleartext/separate) |
Two-step activation provisioning
Configuration
To provision authenticators compliant with two-step activation, a new client component must be defined in OneSpan Authentication Server as defined in the website configuration file (controller.properties).
The definition of the client component properties is:
component.type.provisioning.mdl = Multi-Device Licensing Provisioning Sample Client
The required properties of the new client component are:
IP address: IP address of the machine hosting the sample website
Component Type: Multi-Device Licensing Provisioning Sample Client
Policy: IDENTIKEY Provisioning for Multi-Device Licensing
If OneSpan Authentication Server is configured not to use a back-end server, the setting for Policy > Back-End Authentication in the IDENTIKEY Provisioning for Multi-Device Licensing policy should be set to None.
Standard provisioning
Configuration
To provision Mobile Authenticator Studio 4.0 authenticators, the configuration file must be updated as described in Mobile Authenticator Studio 4.0 configuration. In that case, the configuration file is used as the input to the Mobile Authenticator Studio Midlet Customization Tool.
After updating the required binaries, the SMS gateway needs to be updated to enable Mobile Authenticator Studio provisioning. To enable distribution of the Mobile Authenticator Studio midlet, the SmsGateway.properties file must be defined at the following location:
webapps_folder/OASSampleSite/WEB-INF/classes/SmsGateway.properties
# SMS Gateway address: # This MUST contain the following substitution strings: # %phone_id% : mobile phone number # %sms_text% : message text # Example: # http://www.smsgateway.com/http/sendmsg?user=user&password=password&api_id=123456&to=%phone_id%text=%sms_text% request_URL= # The text pattern used to match the SMS gateway server error response. fail_text=