Overview
JWT (JSON Web Token) authentication is a standard method for securely verifying user identity. By implementing JWT authentication, you add a critical layer of security to your data collection process with MoEngage. The feature ensures that the data sent on behalf of your identified users is authentic and is not tampered with. This security is achieved by requiring a token that is cryptographically signed by your own server, which prevents unauthorized users from impersonating your legitimate users.Before you begin the implementation, ensure you meet the following requirements:
- Your application must use the MoEngage Android SDK version 14.04.00 or higher to access the JWT authentication feature.
- You must have access to your MoEngage dashboard to manage public keys and configure the feature’s enforcement settings.
.jpeg?fit=max&auto=format&n=Jtvf10ggM77HdKvB&q=85&s=c9c81f1b45cf152e3109ada2c2538739)
Integration
Perform the following to integrate JWT authentication into your Android application:Step 1: Enable JWT Authentication
You can enable JWT authentication during SDK initialization by configuring the NetworkAuthorizationConfig property on the MoEngage.Builder object.Step 2: Pass the JWT to the SDK
Your application is responsible for managing the JWT lifecycle. The recommended flow is to fetch a token upon user login and pass the token to the SDK. You should also check if the token has expired on subsequent app launches and fetch a new one if necessary. Use the MoECoreHelper.passAuthenticationDetails() to provide the token to the SDK.Step 3: Handle Authentication Errors
To handle token validation errors that the MoEngage server returns, you must register an error listener. The SDK invokes this listener when an authentication error occurs, which allows your application to fetch and provide a new token.Step 4: Handle Authentication Errors
Register the OnAuthenticationError listener in a global scope, such as the onCreate() of your Application class, to ensure your application always receives callbacks.- If an API request fails due to an authentication error, the SDK will not retry the request until your application provides a new token.
- After 10 consecutive authentication failures in a single session, the SDK will stop attempting to sync data until the next session begins. This counter resets after any successful sync.
- Upon user logout, if a data sync fails due to a JWT error, the pending data will be deleted, and no retry will be attempted.