PingID Mobile SDK 1.0.2 (21 February 2018) - PingID

Enhancements

Registration modes

During a device pairing process, PingID SDK attempts to pair using remote notifications. When successful, the paired device can receive push notifications for ongoing authentication and transaction approvals. If the remote notifications fail, PingID SDK attempts to pair without remote notifications, in which case the paired device can be used as an authenticating device using a one time passcode.

In addition to the existing registration mode (remote notifications with automatic fallback to one time passcode) as described above, PingID mobile SDK has now been extended to support a greater diversity of registration modes. There are now also the options to restrict device registration to either a mode using remote notifications exclusively, or to a mode using a one time passcode exclusively.

Device registration without verification

Device registration has been extended to allow the ability to define the option for an existing active user to pair a new device without the need to verify the new device via the primary device.

Resolved issues

SDK code changes

PingID SDK component dependencies in build.gradle (Android)

This version includes new SDK component dependencies for Android. These should be added in the application's gradle.build file under dependencies. Developers must manually add these dependencies to their project, in order for the SDK to work, as the lib is distributed as a file and not via a repository.

The full list of dependencies is as follows:

compile 'org.slf4j:slf4j-api:1.7.7'
compile 'com.github.tony19:logback-android-core:1.1.1-6'
compile('com.github.tony19:logback-android-classic:1.1.1-6') {
    exclude group: 'com.google.android', module: 'android'
}
compile 'com.nimbusds:nimbus-jose-jwt:4.11'
compile 'com.google.code.gson:gson:2.6.2'
compile 'commons-codec:commons-codec:1.5'
compile 'com.madgag:sc-light-jdk15on:1.47.0.3'
compile 'com.madgag:scprov-jdk15on:1.47.0.3'
compile 'com.google.android.gms:play-services-base:10.2.1'
compile 'com.google.firebase:firebase-messaging:10.2.1'

Refer to Getting started with Android in PingID SDK for details.

Note:

Developers upgrading from PingID SDK 1.0.0 should replace the dependency

compile 'io.jsonwebtoken:jjwt:0.7.0'

with

compile 'com.nimbusds:nimbus-jose-jwt:4.11'

as reflected in the updated dependency list above.

Registration mode for pairing (Android and iOS)

The new registration modes use the Supported MFA type parameter, which must be added into the PingID SDK initialization:

• Android:
  Backward compatibility is maintained with the old initialization

  PingID.init(<Android application object>, <Application ID>, <Object implementing PingIDSDKEvents>,<Push sender ID>);

  which will continue to support remote notifications with automatic fallback to one time passcode.

  In order to specify the registration mode, initialize the PingID SDK singleton, as described in the initialization step at Getting started with Android in PingID SDK, and repeated below with the new registration mode (Supported MFA type) parameter:

  PingID.init(<Android application object>, <Application ID>, <Object implementing PingIDSDKEvents>,<Push sender ID>, <Supported MFA type>);

  Arguments:

  • Android application object: The Android application instance of the customer mobile application.
  • Application ID: The application identifier from the Ping Identity web portal.
  • Object implementing PingIDSDKEvents: The object which implements the PingIDSDKEvents interface.
  • Push sender ID: The GCM/FCM sender ID.
  • Supported MFA type: The registration mode for pairing. Possible values:

    Registration mode value	Description
    Automatic	MFA supports remote notifications with automatic fallback to one time passcode.
    EnforceRemoteNotifications	MFA supports remote notifications only.
    DisableRemoteNotifications	MFA will not support remote notifications and will only support one time passcode.

• iOS:
  Backward compatibility is maintained with the old initialization

  + (void)initWithAppID:(nonnull NSString *)appID

  which will continue to support remote notifications with automatic fallback to one time passcode.

  In order to specify the registration mode, use the new initialization:

  + (void)initWithAppID:(nonnull NSString *)appID supportedMfa:(PIDSupportedMfaType)supportedMfaType;

  defined as follows:

  /**
   Supported MFA types
   
   - PIDSupportedMfaTypeAutomatic:                   MFA supports remote notifications with automatic fallback to one time passcode
   - PIDSupportedMfaTypeEnforceRemoteNotifications:  MFA supports remote notifications only
   - PIDSupportedMfaTypeDisableRemoteNotifications:  MFA will not support remote notifications and will only support one time passcode
   */
  typedef NS_ENUM(NSUInteger, PIDSupportedMfaType)
  {
      PIDSupportedMfaTypeAutomatic                  =   0,
      PIDSupportedMfaTypeEnforceRemoteNotifications =   1,
      PIDSupportedMfaTypeDisableRemoteNotifications =   2
  };

Known issues and limitations

Initializing a second pairing before completion of the first pairing process on the same device

If a user starts a new pairing process on a device which is still running the process of a previous attempted pairing, it may cause a race condition (Android and iOS).

• If the admin console shows that a device or multiple devices are paired with the server, but the user cannot authenticate, then admins should unpair the affected devices, and the user should start a new pairing process.
• Developers should create the necessary logic in their applications to prevent users from initiating a new pairing process while there is already a pairing request in progress.