User and device management
The Keyless SDK "caches" the enrolled user locally on the device.
There are some use cases where it is possible to delete the user from server API and delete the device from server API. The Keyless SDK will not be notified about such deletions. For this reason if you try to authenticate a user or a device that have been deleted from server API you will get an error.
The Keyless SDK offers a way to check if you are in this situation: you can use the validateUserAndDeviceActive
API. This will validate that both the user and the device are still "active" (i.e. they exist) in the Keyless backend.
You may want to call validateUserAndDeviceActive
before an authentication to avoid going through the user biometric extraction if the user has been deleted.
User identifier
To retrieve the user identifier you can use the Keyless.getUserId()
api
Device identifier
The device is identified by means of its public signing key. To retrieve the device identifier you can use the Keyless.getDevicePublicSigningKey()
api:
Keyless SDK reset
Sometimes it may be useful to reset the Keyless SDK to a clean state.
Note: this will not de-enoll the user from the Keyless backend or deactivate the device from the Keyless backend.
After the reset the Keyless SDK local data will be deleted. You can use the Keyless.reset()
api to reset the Keyless SDK:
Last updated