Skip to end of metadata
Go to start of metadata

Overview

AMS has a variety of different features that can help provide extra security for your messages. These include SSL encryption for transport security and device locking for lost or stolen handsets.

Network Security With HTTPS

You can use HTTPS connections instead of HTTP connections for all mobile to server communications. To do this, choose settings from the menu within AMS and set 'Use SSL' to be "on".

MIDP Client

BlackBerry Client

Template routes can also be set to deliver to HTTPS endpoints.

Device Locking

Mobile Accounts can be locked after being authenticated. This prevents the same mobile account being used on another device until it is unlocked. When a previously locked mobile account is unlocked a new device key is generated. Previously authenticated devices will have to login again to AMS. New mobile accounts are initially unlocked.

To have mobile accounts automatically lock after successful authentication select the "Lock Mobile Accounts" option in the account settings on the web.

To lock an individual mobile account, edit that account and click the "Lock Mobile Account" button.

To unlock a previously locked mobile account, edit that account and click the "Unlock Mobile Account" button.

A Web Service API method to lock and unlock mobile accounts will be available shortly.

Generating Device Keys

Once a mobile user has authenticated on their phone they are assigned a device key. This key is then used in future communication with the AMS server. If you want to force the generation of a new device key, edit the desired mobile account and click the "Generate New Device Key" button.

Save the changes to enable the new device key. When the mobile user's phone next communicates with the AMS server they will be required to re-authenticate.

Labels: