New in this release (6.0.1.37):
- Support for programmatic activation with BlackBerry Dynamics SDK 6.0 or later.
- Class123Skelton has been enhanced to demonstrate how to programmatically activate a DAF application.
- Support migration of applications from GC to UEM with BlackBerry Dynamics SDK 6.0 or later.
Release 4.2.0.30:
- Bug fixes and general improvements.
Release 2.1.171:
- User interface changes to support Easy Activation using DAF-based applications. This will require changes to application code, see Appendix - Authentication With Warning (Android) for details. IMPORTANT: Existing DAF applications will fail to build with the new SDK until these changes are made.
Release 1.11.125
- Fix issue GD-8669. The getMechanisms() method is now attached to the DAKey class, not DADevice. This allows each key to report which crypto mechanisms it supports. Example code has been updated to reflect this.
- Fix issue GD-8683. Keys which have the DA_USER_AUTHENTICATE attribute flag set are now asked to generate signatures (via the sign() method), and not encryption and decryption.
Release 1.9.17
Correct bug in temporary unlock flow if we receive events from GD in an unexpected order after temporary unlock completes.
Release 1.9.16
The first two digits of DAF version numbers now match the GD SDK they were tested with.
The TestRequester app has been removed from the distribution. Please use a GD sample app delegating authentication to your authenticator to test your app.
The native examples for class 2, 3 and 4 devices were removed from the distribution. Please contact Good customer support if you need additional native example code. The class 0 and 1 native and all Java examples remain.
DAF is now compatible with Android 5.0 'Lollipop' and GD release 1.9.1162. Native libraries now use the 'armeabi-v7a' ABI.
Bugs have been fixed in the Class0BLE and Class1NFC samples.
The SDK can now be installed using the Android SDK manager.
Release 1.1.36
The Android example apps have had their native app IDs changed to match their GD app IDs. The apps are now:
- com.good.example.daf.class0ble
- com.good.example.daf.class0nfc
- com.good.example.daf.class1nfc
- com.good.example.daf.class3keystore
This corrects compatiblity with GD versions 1.8.* and later.
Additionally, an error handling bug was fixed in the DAF JNI layer.
Release 1.1.32
- Now suitable for use with GD SDK 1.7.
Release 1.0.0
This is the initial release of the Digital Authentication framework.
Known issues in 1.0.0:
- This code MUST be used in conjunction with release 1.6 or later of the Good Dynamics SDK. It will not work with earlier versions.
- S/MIME is not supported in this release.
- Support for custom authenticator policies is planned for a later release of Good Dynamics software.
