Using Deep Links To Apply A PIN On Android Devices
This article explains how to use deep links (intents) to automatically configure the NowSignage Android application with an authentication PIN. It is intended for integrators and device management systems (MDM) such as SOTI, ADB, or any tool capable of sending intents to Android devices.
Compatibility: This feature is supported on Android app version 5.2.52 and above only.
Intent Format:
General Scheme
nowsignage://configure?json=<JSON_URL_ENCODED>
JSON Format
The JSON payload should include the pin_code to configure the device. Note: The PIN in examples is illustrative; replace it with the actual screen PIN.
{
"pin_code": "18583"
}
Important: The JSON must be URL-encoded before including it in the deep link.
Commands to Send the Intent:
1. SOTI (Send Intent)
sendintent -a "nowsignage://configure?json=%7B%22pin_code%22%3A%2212345%22%7D#Intent;action=android.intent.action.VIEW;category=android.intent.category.BROWSABLE;component=com.nowsignage.app/.MainActivity;end"
2. ADB (Android Debug Bridge)
adb shell am start -a android.intent.action.VIEW -d "nowsignage://configure?json=%7B%22pin_code%22%3A%22123456%22%7D" -n com.nowsignage.app/.MainActivity
3. Open from an Android Browser
If the device allows opening deep links from a browser:
nowsignage://configure?json=%7B%22pin_code%22%3A%22123456%22%7D
Rules for pin_code:
-
Must be 5 to 8 characters long.
-
Can include letters and numbers only (a-z, A-Z, 0-9).
-
No spaces or special characters allowed.
Valid Intent Examples
nowsignage://configure?json=%7B%22pin_code%22%3A%2212345%22%7D
nowsignage://configure?json=%7B%22pin_code%22%3A%22AB1234%22%7D
Expected Behaviour in the App
-
The app receives the intent with the pin_code.
-
It validates the format and checks the code against the server.
-
If the PIN is correct, the screen configures automatically.
-
If the PIN is incorrect, an error message is displayed.