In this post, I would build a scenario where the target audience would need to authenticate themselves with the fingerprint configured on their phone before they read their message. Similarly, you could build actions that need fingerprint (or other auth mechanisms) for attendance marking, acknowledge a message, etc.
Building the card
Kaizala action package SDK has an API performAuthenticationAsync, that allows you to authenticate / verify user via a host of options like fingerprint, pattern, pin, password and face recognition. Below is the screenshot of the API from KASClient SDK:
We will build a custom action that allows the sender to type in a message that would get sent as a property in the card sent to users on the group. On opening the card, we will call the API to validate the user’s fingerprint and display the message on successful verification. Else, display an error message.
In the creation view, a simple input box which takes the message as input from the sender and a submit button that creates / sends the card on the group. Below is code snippet from the sample:
In the response results view, we would request for the fingerprint verification and decide whether to display the message (on successful verification) or show the error message (on verification failure).
Below is a screen recording of how the card looks in action:
Hope that was helpful in introducing the auth options provided by KASClient SDK. In case you have any comments / questions, feel free to contact me via the contact page.
The code for this sample has been shared here.