Overview

In the Mobile Protector SDK, some sensitive functionalities are represented by the EMPasswordDomain. Each element of the enum EMPasswordDomainType represents a specific set of functionalities. Before these functionalities can be used, they must first be unlocked.

The Password Manager is a high level interface that allows to set a single password to manage all the EMPasswordDomain at the same time.

Using User-defined Password

1. Set a password. The first step when using the EMPasswordManager is to set a password. The password should be provided by an outside source (the application user, through a secured communication channel with a server, etc.).

    // Assumptions
    // get PasswordManager from EMEzioMobileContext and assign it to 'passwordManager'
    // then...
    BOOL isSetResult = [passwordManager isPasswordSet:&error];
    if (!isSetResult) {
        // manage error here
    }else{
        // get password and store it in 'userProvidedPassword' string or data.
        // get EMSecureDataFactory from EzioMobileContext and assign it to 'secureDataFactory'
        EMSecureString password = [secureDataFactory secureStringWithString:userProvidedPassword];
        BOOL result = [passwordManager setPassword:&error];
        if (!result) {
            // manage error here
        }
    }
   

2. Login. Next, you simply need to login using loginWithPassword:error: or its asynchronous equivalent -loginWithPassword:completionHandler: to unlock all functionalities represented by the EMPasswordDomain. The EMPasswordManager will remain logged in until logout: is called.

No Password

1. If you wish to use the functionalities represented by the EMPasswordDomain without the use of a password, use login: or its asynchronous equivalent –loginWithCompletionHandler: to login without using a password. As long as no password was set, you can call login: without needing to provide a password.

• Usage of the SDK without setting a proper password is strongly discouraged as it introduces a serious security weakness in your application. Note that as long as the [login:](#//api/name/login:), -loginWithPassword:completionHandler:, [removePassword:error:](#//api/name/removePassword:error:) or -removePassword:completionHandler: methods are never used, no security weakness will be introduced even if the password is not yet set.
• Password domains are protected with passwords and reside in the `Documents` directory of an your application container. **Be very careful when managing local files as this will have severe impact on the SDK's operations** such as when those files generated by the SDK are accidentally deleted using `NSFileManager`.
• Tasks can take considerable amount of time and may potentially block the UI if executed on the main thread.

Also see: EMEzioMobileContext, EMPasswordDomain