The AuthenticAction Service
Last updated
Last updated
The AuthenticAction Service is a platform which supports the Client SDKs, and includes the following main components:
In order to secure client sessions, the service includes endpoint services that are reserved for communication between client SDK components and the AuthenticAction Service.
The AuthenticAction REST API provides and efficient interface for your back-end services to validate a session and parameters presented by a client. With the bank client integrated with the AuthenticAction SDK secure communication is established between the client and the AuthenticAction service; this connection is referenced by a session id. When your server receives a data posting (for example, a transaction), validation of those details is accomplished through the "validate" REST endpoint, as detailed in this section.
A biometric template for a new user is added to the system in a processed called biometric enrollment. Normally a new user can be added in a passive manner (passive enrollment), meaning the user template will be created based on the biometric frames collected during the first ever user's interaction with the AuthenticAction Service. If you wish to keep the enrollment process in control, the Service can be configured to allow only Active Enrollment. Please contact IronVest support to make sure your service is configured accordingly. You need to explicitly indicate that the Active Enrollment is taking place by setting the value of isEnrollment flag in .
If Active Enrollment is enforced, the biometric matching will fail, unless the current user matches a biometric template of the user that was previously ACTIVELY enrolled to biometrics.
The AuthenticAction Dashboard provides a management view of client SDK sessions. typically, automation is achieved through REST API calls, and the dashboard component is reserved for any manual inquiries related to investigations.
Note: Layout and features of the AuthenticAction Dashboard may vary based upon licensed components as well as which features your team has configured (for example, hashing of data, storage of forensic images, etc.).
