This library is designed to provide additional authentication flows for your applications.
In order to correctly integrate the authentication library within your application, please make sure that you have successfully integrated the Android SDK v4.x core library, as it is a mandatory dependency for using the new authentication flows.
Add the Authentication library archive implementation to your application build.gradle file.
Remote Login Verification
Remote login verification is an authentication flow that uses the Android device as a verification factor when initiating a login request from your site.
To enable this authentication method, follow the below steps to configure your site.
For more information on configuring your Polices for TFA, see Authentication Types.
Registering your application to receive remote authentication push messages is available using the following implementation steps:
For successfully receiving a push notification in your application you will need to define the GigyaFirebaseMessagingService in your AndroidManifest.xml file.
f your application already uses FirebaseMessagingService, you will be required to make your service class implementation to extend the GigyaFirebaseMessagingService. This will not break any of your remote messaging flows in any way. Please make sure to call the main "super" functions to allow the GigyaFirebaseMessagingService to perform its own logic.
Update your AndroidManifest.xml file as follows:
In addition, you are required to register the AuthPushReceiver.java class. This class will intercept verification actions that are visible in the incoming remote notifications.
In order to correctly initialize the library, call the "registerForPushNotification" library function from your entry point activity. This function will query your application settings to make sure that notification permission is enabled for this service. In the case, settings are disabled the SDK will issue a notice dialog.
The Verification Flow
In order to begin the verification flow, your device needs to be registered for this service.
Device registration is done by calling the library registerForAuthPush method.
Once your device is successfully registered, in the event of a login attempt from the web, your device will receive a push notification allowing us to choose if you wish to approve or deny the login attempt. thus providing an additional layer of authentication.
The verification notification should look as follows:
Available Customization Options
The SDK provides additional customization options for your TFA specific remote messages & the option to use your own customized activity for remote actions (approve/deny).
Note: Using a customized action activity is mandatory when using fingerprint session encryption. A detailed example is provided further down this tutorial.
In order to provide customization please use the following method: