EMOtpModule Class Reference

Inherits from	NSObject
Declared in	EMOtpModule.h

Overview

OtpModule class which is the entry-point for OTP features.

`+ otpModule`

Create OtpModule object.

+ (EMOtpModule *)otpModule

Return Value

Otp Module.

Availability

4.0

Declared In

EMOtpModule.h

`– updateDeviceFingerprintTokenPolicyWithTokenName:oldCustomData:newDeviceFingerprintTokenPolicy:error:`

To apply the new device fingerprint policy to the token. This API will change (add or remove) the device token policy ‘EMDeviceFingerprintTokenPolicy’ properties, such as:

The mode 'failIfInvalid'
The custom fingerprint data
The fingerprint source type 'EMDeviceFingerprintSource'

- (BOOL)updateDeviceFingerprintTokenPolicyWithTokenName:(NSString *)tokenName oldCustomData:(NSData *_Nullable)oldCustomData newDeviceFingerprintTokenPolicy:(EMDeviceFingerprintTokenPolicy *)newDeviceFingerprintTokenPolicy error:(NSError **)error

Parameters

`tokenName`	The token name
`oldCustomData`	The old custom fingerprint data (if any) NOTE: The application manages the custom fingerprint data value so that it uses the proper value while retrieving the token, for example, by calling [capTokenManager tokenWithName:fingerprintCustomData:error:];
`newDeviceFingerprintTokenPolicy`	The new device fingerprint token policy. NOTE: The application has to retrieve the token object again to update the changes, for example, by calling [capTokenManager tokenWithName:fingerprintCustomData:error:];
`error`	If an error occurs while migrating the token, upon return contains an NSError object that describes the problem. Update may fail due to: If the new DeviceFingerprintTokenPolicy and old policy are identical. If the provided 'oldCustomData' does not match with the one while creating the token If there is no token present with the specified token name.

Return Value

YES if the migration is successful else returns NO

Declared In

EMOtpModule.h