The following two chapters list all notable in-code changes of the XignSys SDK between version 4.2.X and 4.3.0.
Personalizer:
startDeletion & startDeletionSynchronousfinishDeletion & finishDeletionSynchronousApiAccessDelete of AuthenticationResult.XignSdkErrorCodes.SERVER_REGISTRATION_INVALID_SERVICE_MAPPING_ID.RegistrationInitializationErrorCodes.INVALID_SERVICE_MAPPING_ID.serviceMappingId to functions initialization & initializationSynchronous of
the Registry.RegistrationParameters changes:
serviceMappingId: String.arbitraryUserAttributes: Map<String, String>.setArbitraryUserAttributes(:).RegistrationParameters changes:
alias: String?.validatorAlias: String.setAlias(:).alias to PersonalizationResult.alias to IdentityManagerEntity. (Includes database migration)RegistrationResponseFailure.RegistrationResponseSuccess which represents all possible successful registration
results. This has been done in preparation of the e-mail-less registration.RegistrationResponseSuccessDone which replaces the old RegistrationResponse.Success and
therefore contains managerUrl so it can still be accessed.RegistrationResponse from package .registration to new subpackage .registration.result.RegistrationResponse from being a sealed class to a sealed interface.Failure from RegistrationResponse - Replace with RegistrationResponseFailure.Success from RegistrationResponse - Replace with RegistrationResponseSuccessDone..dto to .dto.process.initialization:
AuthenticationInitializationDataAuthenticationInitializationDataInAppAuthenticationInitializationDataWithSessionPersonalizationInitializationDataProcessInitializationDataTransactionInitializationDataAuthenticationResult from package .authentication to .authentication.result.
AuthenticationResult type from sealed class to sealed interface.val idmIdentifier: String to AuthenticationResult..authentication.result,
e.g. com.xignsys.sdk.dto.authentication.AuthenticationResult.UserLoginResult is
now com.xignsys.sdk.dto.authentication.result.UserLoginResult. Affected classes are:
AuthenticationResult.ApiAccessAddFactor -> ApiAccessAddFactorAuthenticationResult.ApiAccessChangePin -> ApiAccessChangePinAuthenticationResult.ApiAccessMergeComplete -> ApiAccessMergeCompleteAuthenticationResult.ApiAccessRequestNewActivationData -> ApiAccessRequestNewActivationDataAuthenticationResult.Lockout -> LockoutAuthenticationResult.ServiceLoginResult -> ServiceLoginResultAuthenticationResult.UserLoginResult -> UserLoginResultSerializable implementation of Lockout.XignSdkErrorCodes.UNEXPECTED_ERROR was returned instead of a XignSdkErrorCodes.DEVICE_LOCKED if an
Android UserNotAuthenticatedException was raised during the key access. This seems to be the case for some
devices with "Face Unlock", as the system probably classifies "Face Unlock" as insufficient for authentication.
For more information please take a look at the documentation of the XignSdkErrorCodes.DEVICE_LOCKED error code.