Enforce identity verification on all platforms to prevent third parties from impersonating logged-in users.
Once enabled, Gleap will require you to pass the correct user hash in order to identify users.
For private conversation attachments, also follow Authenticated conversation files. That guide covers the compatible SDK, customer application URL and preserving attachment links through login. Identity verification alone does not enable protected file storage.
User hash generation
To set up identity verification, you’ll need to generate an HMAC on your server for each logged-in user and send it to Gleap.
Please choose your server stack to show an example code for the user hash generation.
NodeJS
Rails (Ruby)
Django (Python 3)
PHP
Important: Gleap handles the userId as STRING, please make sure to convert the user ID to a string, before generating the hash.
Keep your secret key safe! Never commit it directly to your client-side code, or anywhere a third party can find it.
Indentify user with user hash
After generating the user hash you need to send it to your client and pass it to the Gleap SDK.
JS
iOS
Android
ReactNative
Flutter