Migration from 1.9.x to 1.10.x
PowerAuth Mobile SDK in version 1.10.0 provides the following improvements:
- PowerAuth mobile SDK no longer supports activation by the recovery code.
- New
PowerAuthBiometricConfigurationclass that simplifies biometric configuration ofPowerAuthSDKclass. - PowerAuth mobile SDK now ensures sensitive keys are not retained in memory.
Compatibility with PowerAuth Server
- This release is fully compatible with PowerAuth Server version
1.9.0and newer.
Android
Notable changes on Android:
- New
PowerAuthBiometricPromptclass simplifies biometric key setup and authentication. - Added the
SecureDataclass toio.getlime.security.powerauth.corepackage to enhance in-memory management of sensitive data.
API changes
- The following methods or properties are now deprecated:
PowerAuthSDKclass:changePasswordUnsafe()- use asynchronouschangePassword()as a replacement.persistActivationWithAuthentication()- use asynchronous variant withIPersistActivationListeneras a callback parameter.persistActivationWithPassword()- use asynchronous variant withIPersistActivationListeneras a callback parameter.persistActivation(..., IPersistActivationWithBiometricsListener)- use asynchronous method withIPersistActivationListeneras a callback parameter.- All variants of
addBiometryFactor()with “title” and “description” parameters are now replaced with variant usingPowerAuthBiometricPrompt. removeBiometryFactor()- use asynchronous variant withIRemoveBiometryFactorListeneras a callback parameter.authenticateUsingBiometrics()- with “title” and “description” parameters, use variant withPowerAuthBiometricPromptparameter instead.requestGetSignatureWithAuthentication()- useauthorizationHeaderForRequestWithParams()method instead which throws an exception in case of failure.requestSignatureWithAuthentication()- useauthorizationHeaderForRequestWithBody()method instead which throws an exception in case of failure.
PowerAuthConfigurationclass:getOfflineSignatureComponentLength()- usegetOfflineAuthorizationCodeComponentLength()instead.
PowerAuthConfiguration.Builderclass:offlineSignatureComponentLength()- useofflineAuthorizationCodeComponentLength()instead.
PowerAuthKeychainConfigurationclass:isLinkBiometricItemsToCurrentSet()- usePowerAuthBiometricConfiguration.isInvalidateBiometricFactorAfterChange()instead.isConfirmBiometricAuthentication()- use equal method inPowerAuthBiometricConfigurationinstead.isAuthenticateOnBiometricKeySetup()- use equal method inPowerAuthBiometricConfigurationinstead.isFallbackToSharedBiometryKeyEnabled()- use equal method inPowerAuthBiometricConfigurationinstead.Builder.linkBiometricItemsToCurrentSet()- usePowerAuthBiometricConfiguration.Builder.invalidateBiometricFactorAfterChange(boolean)instead.Builder.confirmBiometricAuthentication()- use equal method inPowerAuthBiometricConfiguration.Builderinstead.Builder.authenticateOnBiometricKeySetup()- use equal method inPowerAuthBiometricConfiguration.Builderinstead.Builder.enableFallbackToSharedBiometryKey()- use equal method inPowerAuthBiometricConfiguration.Builderinstead.
PowerAuthTokenclass:generateHeader()- usegenerateTokenHeader()as a replacement. Note that you should usePowerAuthTokenStore.generateAuthorizationHeader()to make sure the PowerAuth SDK synchronize the time with the server properly.
PowerAuthAuthorizationHttpHeaderclass:- The value of
powerAuthErrorCodeproperty, or value returned ingetPowerAuthErrorCode()is filled only in deprecated SDK functions, such asrequestSignatureWithAuthentication(). To fix this, migrate toauthorizationHeaderForRequestWithBody()that throws an exception in case of failure. isValid()method is also deprecated, because the new methods, such asauthorizationHeaderForRequestWithBody(), always returns the valid header.
- The value of
- The following classes and interfaces are now deprecated:
IPersistActivationWithBiometricsListener- useIPersistActivationListenerinstead.
- Due to removed support of recovery codes, the following classes and methods are no longer available:
- Methods removed in
PowerAuthSDK:createRecoveryActivation()hasActivationRecoveryData()getActivationRecoveryData()confirmRecoveryCode()
- Methods removed in
PowerAuthActivation.Builder:- all variants of
recoveryActivation()
- all variants of
- Methods removed in
ActivationCodeUtil:parseFromRecoveryCode()validateRecoveryCode()validateRecoveryPuk()
- Other removed methods:
CreateActivationResult.getRecoveryData()ErrorResponseApiException.getCurrentRecoveryPukIndex()
- Removed classes and interfaces:
IGetRecoveryDataListenerIConfirmRecoveryCodeListenerRecoveryData
- Methods removed in
- The following functions now takes or returns
SecureDatainstead ofbyte[]:PowerAuthSDK.persistActivationWithPassword()PowerAuthSDK.addBiometryFactor()PowerAuthSDK.setExternalEncryptionKey()PowerAuthSDK.addExternalEncryptionKey()PowerAuthConfiguration.getExternalEncryptionKey()PowerAuthConfiguration.Builder.externalEncryptionKey()PowerAuthAuthentication.getBiometryFactorRelatedKey()PowerAuthAuthentication.getOverriddenPossessionKey()- All static functions in
PowerAuthAuthenticationthat takes custom possession or biometry key in parameter. IFetchEncryptionKeyListener.onFetchEncryptionKeySucceed()CryptoUtils.ecdhComputeSharedSecret()BiometricKeyData.getDerivedData()BiometricKeyData.getDataToSave()
- Removed all interfaces deprecated in release
1.9.x
Other changes
- TBA
iOS & tvOS
Notable changes on iOS:
- Added the
PowerAuthCoreDataobject toPowerAuthCoremodule to enhance in-memory management of sensitive data.
API changes
- The following methods or properties are now deprecated:
PowerAuthSDKclass:unsafeChangePassword(from:to:)- use asynchronouschangePassword(from:to:callback:)as a replacement.persistActivation(with:)- use asynchronouspersistActivation(with:callback:)as a replacement.persistActivation(withPassword:)- use asynchronouspersistActivation(withPassword:callback:)as a replacement.removeBiometryFactor()- use asynchronousremoveBiometryFactor(callback:)as a replacement.- Constructor
PowerAuthSDK(configuration:keychainConfiguration:clientConfiguration:)- use methods withPowerAuthBiometricConfigurationparameter instead. requestSignature(with:method:uriId:body:)- useauthorizationHeaderForRequestWithBody(with:method:uriId:body:)method instead.requestGetSignature(with:uriId:params:)- useauthorizationHeaderForRequestWithParams(with:method:uriId:params:)method with"GET"as method parameter.offlineSignature(with:uriId:body:nonce:)- use asynchronousofflineAuthorizationCode(with:uriId:body:nonce:callback:)method that handle the biometric authentication properly.
PowerAuthConfigurationclass:offlineSignatureComponentLengthproperty is now replaced withofflineAuthorizationCodeComponentLength
- All static methods for accessing a various shared instances are now deprecated:
PowerAuthSDK.initSharedInstance(...)andPowerAuthSDK.sharedInstance()- To ensure better control and flexibility, manage the global instances within your application code.PowerAuthClientConfiguration.sharedInstance()- use a class constructor with no parameters if you want to create the default configuration.PowerAuthKeychainConfiguration.sharedInstance()- use a class constructor with no parameters if you want to create the default configuration.
- The following properties in
PowerAuthKeychainConfigurationclass are now deprecated:linkBiometricItemsToCurrentSet- use newPowerAuthBiometricConfiguration.invalidateBiometricFactorAfterChangeinstead, with the same meaning.allowBiometricAuthenticationFallbackToDevicePasscode- use newPowerAuthBiometricConfiguration.allowFallbackToDevicePasscodeinstead, with the same meaning.invalidateLocalAuthenticationContextAfterUse- use newPowerAuthBiometricConfiguration.invalidateLocalAuthenticationContextAfterUseinstead, with the same meaning.- Be aware that if you provide both,
PowerAuthBiometricConfigurationandPowerAuthKeychainConfigurationobjects to initializePowerAuthSDK, then the values from the biometric configuration takes precedence.
- Due to removed support of recovery codes, the following classes and methods are no longer available:
- Methods removed in
PowerAuthSDK:createActivation(withName:recoveryCode:recoveryPuk:extras:callback:)hasActivationRecoveryData()activationRecoveryData(authentication:callback:)confirm(recoveryCode:, authentication:callback:)
- Methods removed in
PowerAuthActivationCodeUtil:validateRecoveryCode()validateRecoveryPuk()parseFromRecoveryCode()
- Other changes:
- removed class
PowerAuthActivationRecoveryData - removed property
PowerAuthActivationResult.activationRecovery - removed constructor
PowerAuthActivation(recoveryCode:recoveryPuk:name:)
- removed class
- Methods removed in
- The following functions or properties now takes or returns
PowerAuthCoreDatainstead ofData:PowerAuthSDK.setExternalEncryptionKey()PowerAuthSDK.addExternalEncryptionKey()PowerAuthSDK.fetchEncryptionKey()PowerAuthConfiguration.externalEncryptionKey- All static functions in
PowerAuthAuthenticationthat takes custom possession or biometry key in parameter. PowerAuthAuthentication.overridenPossessionKeyproperty is nowcustomPossessionKeyPowerAuthAuthentication.overridenBiometryKeyproperty is nowcustomBiometryKeyPowerAuthCoreCryptoUtils.ecdhComputeSharedSecret()
- The following methods in
PowerAuthSDKclass now returns cancelable object allowing you to cancel the pending biometric authentication:authenticateUsingBiometry(withPrompt:callback:)authenticateUsingBiometry(withContext:callback:)
- Removed all interfaces deprecated in release
1.9.x
Other changes
- TBA
iOS & tvOS App Extensions
- The
PowerAuth2ForExtensionslibrary is now deprecated and no longer supported and maintained. You can use full feature PowerAuth mobile SDK as a replacement in your app extension.
Known Bugs
The PowerAuth SDKs for watchOS, do not use time synchronized with the server for token-based authentication. To avoid any compatibility issues with the server, the authentication headers generated in your App Extension or on watchOS still use the older protocol version 3.1. This issue will be fixed in a future SDK update.
You can watch the following related issues:
Last updated on Mar 17, 2025 (17:19)
Edit on Github
Send Feedback