/** * Interface that is used to provide biomety configuration for `PowerAuth` class. */ export interface PowerAuthBiometryConfigurationType { /** * Set whether the key protected with the biometry is invalidated if fingers are added or * removed, or if the user re-enrolls for face. The default value depends on plafrom: * - On Android is set to `true` * - On iOS is set to `false` */ readonly linkItemsToCurrentSet?: boolean; /** * ### iOS specific * * If set to `true`, then the key protected with the biometry can be accessed also with a device passcode. * If set, then `linkItemsToCurrentSet` option has no effect. The default is `false`, so fallback * to device's passcode is not enabled. */ readonly fallbackToDevicePasscode?: boolean; /** * ### Android specific * * If set to `true`, then the user's confirmation will be required after the successful biometric authentication. */ readonly confirmBiometricAuthentication?: boolean; /** * ### Android specific * * Set, whether biometric key setup always require a biometric authentication. * * ### Discussion * * Setting parameter to `true` leads to use symmetric AES cipher on the background, * so both configuration and usage of biometric key require the biometric authentication. * * If set to `false`, then RSA cipher is used and only the usage of biometric key * require the biometric authentication. This is due to fact, that RSA cipher can encrypt * data with using it's public key available immediate after the key-pair is created in * Android KeyStore. * * The default value is `false`. */ readonly authenticateOnBiometricKeySetup?: boolean; /** * ### Android specific * * Set whether fallback to a shared, legacy biometry key is enabled. By default, this is enabled for compatibility * reasons. If enabled, `PowerAuth` performs an additional lookup for a legacy biometric key previously shared * between multiple `PowerAuth` object instances. * * If your application uses multiple `PowerAuth` instances, it's recommended to set this configuration to `false`. * This is because the native SDK doesn't properly handle multiple activations with the shared biometric key. * * If set to `false`, the shared key will no longer be accessible, and you may need to reconfigure the biometric factor * for the existing activations on your `PowerAuth` object instances. * * The default value is `true`, so the fallback is enabled. */ readonly fallbackToSharedBiometryKey?: boolean; } /** * Class that is used to provide biomety configuration for `PowerAuth` class. */ export declare class PowerAuthBiometryConfiguration implements PowerAuthBiometryConfigurationType { linkItemsToCurrentSet: boolean; fallbackToDevicePasscode: boolean; confirmBiometricAuthentication: boolean; authenticateOnBiometricKeySetup: boolean; fallbackToSharedBiometryKey: boolean; /** * The default class constructor, respecting a platform specific differences. */ constructor(); /** * @returns `PowerAuthBiometryConfiguration` with default configuration. */ static default(): PowerAuthBiometryConfigurationType; } /** * Function create a frozen object implementing `BiometryConfigurationType` with all properties set. * @param input Optional application's configuration. If not provided, then the default values are set. * @returns Frozen `BiometryConfigurationType` interface with all properties set. */ export declare function buildBiometryConfiguration(input?: PowerAuthBiometryConfigurationType | undefined): Required;