Initializing the Mobile Protector SDK

This page describes the details how to initialize of the Mobile Protector SDK.

Mobile Protector SDK (software development kit) is an authentication mobile solution for e-banking and e-commerce functions such as one-time password (OTP) management, challenge-responses, transaction data signing, data protection, and out-of- band (OOB) communication. It utilizes the user’s mobile device as the security platform. The solution consists of mobile applications based on the Mobile Protector SDK.

If you’ve already downloaded the Getting Started app (Quickstart) and you are not interested in the detailed usage of Mobile Protector SDK, you can skip the details below and jump to the next page: Enrolling mobile for OATH.

Developing with Mobile Protector SDK

Initializing the SDK

Before Mobile Protector SDK can be used, it must be configured and activated. It is best to do it right after the application is launched.

To initialize the SDK, you have to configure each module used in the application:

  1. Ensure that the SDK has not been already configured. This may be redundant in simple scenarios but as the structure of each application is different, the app should not initialize the SDK multiple times.
  2. Prepare an OTP module using default configuration
  3. As the SDK has to be activated with the proper codes, you can simply pass a set of configurations.
// Make sure, that we will always check isConfigured first. Multiple call of init will cause crash / run time exception.
if (![EMCore isConfigured])
    // OTP module is required for token management and OTP calculation.
    EMOtpConfiguration *otpCFG = [EMOtpConfiguration defaultConfiguration];

    // Configure core with given key and set of required modules.
    [EMCore configureWithActivationCode:C_ACTIVATION_CODE()
                         configurations:[NSSet setWithObject:otpCFG]];