API Changes for MT20W Direct

There are changes to existing API integrations that need to be made to use the MT20W Direct USB Feature.

Pre-Requisites

HTTPS Everywhere

All communication between the desktop application and the host server is over HTTPS (i.e. communication is secure/encrypted).  For this you’ll need to install an SSL certificate onto the web server to initiate a secure session with the desktop application. SSL proves to the user that they are really connecting to the site they requested, and not to an attacker masquerading as the end site.

NOTE: Regardless of whether ‘Secured’ or ‘Unsecured’ configuration is selected during MT20W setup, the communication will be ‘Secured’ (using HTTPS) between the host server and the desktop application. Thus, a valid SSL certificate for the web server is required.

Server DNS/IP Configuration Must Match SSL Certificate

SSL certificates are bound to a ‘common name’, which is usually a fully qualified domain name but sometimes are a wildcard name (e.g. *.domain.com) or even an IP address. The configuration (‘DNS’ name or ‘IP’ address) entered for the MT20W must match the ‘common name’ provided in the certificate, or the connection between the web server and desktop application will fail.

• Authentication Changes
• Primary Credential Encryption Changes