Versions 2.0 and later of the Digital Authentication Framework require all applications to support Easy Activation.

Background

GD's Easy Activation (sometimes referred to as 'Activation Delegation') feature allows one GD application to use another to authorise its initial activation, instead of having the user enter an email address and 15-character Access Key. The application responding to an Easy Activation request must display the name and icon of the requesting application, and obtain confirmation from the user before proceeding.

For a DAF application to respond to Easy Activation requests, it must be able to display an application icon and warning message at the start of the authentication process. The user can confirm or reject the request at this stage; if it is confirmed, authentication proceeds in exactly the same way as an ordinary 'unlock' sequence.

UI changes

Prior to SDK version 2.0, the com.good.daf.app.DAFApplication class called a method getAuthenticationActivityClass(), implemented by each DAF application, to obtain the Java class corresponding to the "Unlock application" Android activity.

In 2.0, this method signature is changed to:

Class<?> com.good.daf.app.DAFApplication.getAuthenticationActivityClass (final AuthenticationWarning w)

For an ordinary "Unlock" operation, the w parameter will be null, and the method call behaves as it did in the 1.x SDK. When the parameter is not null, the call should return the class for an Activity which:

Displays an icon and warning message to the user.
Has an option for the user to cancel the requested operation.

The application designer can choose modify the existing "Unlock" activity to add these warnings, or implement a new activity. The icon and warning message can be retrieved from the AuthenticationWarning object passed into getAuthenticationActivityClass(). Alternatively you can call getAuthenticationWarning() method to return the same object.

If the user chooses to cancel the request, the activity should call rejectAuthenticationRequest() and then terminate. If the user chooses to proceed, the activity should proceed in the same way as for the "Unlock" case i.e. by getting an AuthProcessParams object from DAFApplication.authenticate() and running it.

For the DAF SDK version 2.0.x the only operation which can generate authentication-with-warning requests is Easy Activation (REASON_EASY_ACTIVATION). Future SDK releases may include different types of request; the application should be designed to deal with these in the same way.