Passwordless activation
š Passwordless Activation in REL-ID
ā
What is Passwordless Activation?
Passwordless activation refers to an onboarding flow in which the user is not required to set or enter a password. Instead, alternative secure methods such as OTPs, activation codes, or document-based ID verification (IDV) are used to authenticate and register the user and their device.
š ļø Methods Used in Passwordless Activation
| Method | Description |
|---|---|
| š¢ Activation Code | One-time code issued by backend (via helpdesk, SMS, email) and validated during activation. |
| š© Email OTP / š± SMS OTP | Temporary code sent to userās registered email/phone. Entered during activation. |
| šŖŖ IDV (Document + Selfie) | Identity verified via official document and live selfie capture. |
| š« Pre-Provisioned Secure Token | Admin issues pre-authorized session/token to initialize user device without credentials. |
š Benefits of Passwordless Activation
- Improved UX: No password complexity or resets.
- Higher Security: One-time codes or biometrics reduce password reuse risks.
- Mobile-First: Optimized for app flows where biometric or OTP login is more natural.
- Enterprise-Friendly: Suits managed devices or field staff with limited UI needs.
š§ How SDK Handles It
- The REL-ID SDK skips the
getPasswordevent entirely. - Backend config (
IS_USER_PASS = false) determines this behavior. - Activation completes using OTP + LDA + optional IDV/secret questions.
š§ Passwordless Activation Flow (Mermaid Diagram)
flowchart TD
A["š App Launches & Calls initialize()"] --> B["š getLoginId"]
B --> C["š” setUser()"]
C --> D["š¢ getActivationCode or OTP"]
D --> E["š setActivationCode() or setOTP()"]
E --> F{"š§ IDV Required?"}
F -- "ā
Yes" --> G["šø IDV Document Capture + Selfie"]
G --> H["š§¾ Confirm IDV Verification"]
H --> I["āļø Proceed"]
F -- "ā No" --> I
I --> J["š getUserConsentForLDA"]
J --> K["ā
setUserConsentForLDA()"]
K --> L["š onUserLoggedIn"]
š Developer Notes
- Make sure password step is not forced in backend challenge configuration.
- Use event handlers to skip
setPassword()if it's not triggered. - Ensure LDA and OTP flows are tested across edge cases.
Updated 9 months ago
