OTP Configuration
Defines OTP generation, validation, and resend behavior for passwordless authentication flows.
Table name: otp_config
| Field | Type | Description |
|---|---|---|
| tenant_id | CHAR(10) | Tenant identifier (Primary Key) |
| is_otp_mocked | BOOLEAN | Whether OTP is mocked for testing |
| otp_length | INT | Length of OTP codes |
| try_limit | INT | Maximum number of OTP attempts |
| resend_limit | INT | Maximum number of OTP resend attempts, not including the first one that is implicitly sent via init |
| otp_resend_interval | INT | Minimum interval in seconds between OTP resends |
| otp_validity | INT | OTP validity duration in seconds |
| whitelisted_inputs | JSON | Whitelisted OTP input patterns |
Prerequisites
Section titled “Prerequisites”- Tenant Configuration - A tenant must be created first
- Client Configuration - Required for all flows
- Token Configuration - Required for all flows
- User Configuration - Required for all flows
Related Configurations
Section titled “Related Configurations”For SMS-OTP flows, you also need:
- SMS Configuration - For sending OTP via SMS
For Email-OTP flows, you also need:
- Email Configuration - For sending OTP via Email
See SMS/Email Service Integration for detailed integration information.