Contact Verification Configuration
For verifying phone numbers or email addresses (e.g., during account setup or password reset).
Table name: contact_verify_config
| Field | Type | Description |
|---|---|---|
| tenant_id | CHAR(10) | Tenant identifier (Primary Key) |
| otpLength | INT | Length of the OTP code to be generated |
| tryLimit | INT | Maximum number of verification attempts allowed |
| isOtpMocked | BOOLEAN | Whether to use mock OTPs for testing purposes |
| resendLimit | INT | Maximum number of times OTP can be resent |
| otpResendInterval | INT | Minimum time (in seconds) that must elapse before requesting another OTP |
| otpValidity | INT | Duration (in seconds) for which the OTP remains valid |
| whitelistedInputs | JSON | Map of allowed input patterns for different channels |
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”Contact verification also requires:
- SMS Configuration - For phone verification
- Email Configuration - For email verification
See SMS/Email Service Integration for detailed integration information.