nevis_mobile_authentication_sdk_android 3.3.0
nevis_mobile_authentication_sdk_android: ^3.3.0 copied to clipboard
Android implementation of the nevis_mobile_authentication_sdk plugin
3.0.1 #
- Initial release.
3.1.0 #
- From this version on, the deregistration operation does not require the
aaidto be provided. Providing noaaidin the operation leads to the whole account being deregistered instead of a single authenticator. - We now support class 2 sensors for the biometric authenticator on Android platform.
- Updated Nevis Mobile Authentication SDK for Android to version 3.1.0.
- Deregistration in the Identity Suite environment is not working when cookie renewal is enabled on the backend.
3.2.0 #
- Updated Nevis Mobile Authentication SDK for Android to version 3.2.0.
- We now support disabling the device passcode as fallback for the biometric authenticator. See
Registration.allowDevicePasscodeAsFallback,AuthCloudApiRegistration.allowDevicePasscodeAsFallbackandOutOfBandRegistration.allowDevicePasscodeAsFallback. - We now support adding a retry strategy to the device information change operation.
- The
authenticationRetryIntervalandauthenticationMaxRetriesproperties have been removed from theConfigurationobject. Use theAuthentication.retryPolicyObtainingAuthorizationProviderinstead. - We fixed the deregistration operation, the SDK now fully supports the nevisProxy cookie renewal feature.
3.3.0 #
- Updated Nevis Mobile Authentication SDK for Android to version 3.3.0.
- We now support invalidating the FIDO UAF credentials of biometric and fingerprint authenticators when the user adds new biometric credentials in the OS settings, see
Registration.invalidateOnNewOsBiometrics. - We now support providing HTTP request headers that can be sent in the HTTP request during all the operations, see
requestHeaders. - From this version on, the
LocalData.deleteAuthenticatormethod does not require theaaidto be provided. Providing noaaidleads to all authenticator data being deleted. - Removed property validation for all operations as they are now handled by the native SDKs.