KB_150182: MDC configuration for provider CM on IDENTIKEY Authentication Server.9/11/2017 12:45:40 PM
This document describes how to configure the Message Delivery Component (MDC) for a specific SMS gateway provider (CM). This was tested on IAS 3.11.
One type of DIGIPASS is the VIRTUAL DIGIPASS. A VIRTUAL DIGIPASS uses an SMS to deliver a One Time Password to a User’s mobile phone. The User then logs in to the IDENTIKEY Authentication Server using this One Time Password. There are 2 kinds of VIRTUAL DIGIPASS: The Primary and Backup VIRTUAL DIGIPASS. Both require a configured MDC component. The MDC component requires an SMS Gateway to deliver the One Time Password to a mobile phone. CM is such an SMS Gateway provider. This KB explains how to setup the configuration for this provider.
Gateway Settings TAB
When you have an account with CM a producttoken or api token is generated for you with the following format: 00000000-0000-0000-0000- 000000000000Use this to fill in the User name field. The Password field can be left empty as it is not used.
The Profile name field can be filled with an arbitrary chosen name. In this example we choose CM.
The URL field should be filled in with the url of the CM http gateway which is:
Query and Result TAB
Fill in the Query string field with:
Add 2 rules under Result Matching Rules. One named Success and one named Failure.
For Success, the matching pattern should be:
The Audit text can be anything you choose.
For Failure, the matching pattern should be:
Once the configuration is done you can test it using the test button.
Applies to: IDENTIKEY Authentication Server, Message Delivery Component
KB 150182– 11/09/2017
© 2017 VASCO Data Security. All rights reserved.