Configuration: Allowed Authentication Factors
šÆ Purpose
Controls which authentication factors are available to users during the login process. This configuration directly impacts the user authentication experience and determines the security levels enforced by the system.
š Configuration Location
- Module: Auth Server
- Configuration Name:
allowed.auth.factors - Access Path:
Module Config Management ā Auth Server ā allowed.auth.factors
š Available Configuration Parameters
| Parameter | Type | Default Value | Description |
|---|---|---|---|
rememberMe | boolean | true | Enables browser remember functionality |
smsOtp | boolean | true | Enables SMS OTP as Level 2 authenticator |
emailOtp | boolean | true | Enables Email OTP as Level 2 authenticator |
alwaysAskForPassword | boolean | false | Forces password requirement for all users |
š§ Parameter Details
š rememberMe
- Function: Controls browser remembering capability
- When Enabled: Users see "Remember Me" checkbox during authentication
- User Experience: Selected browsers remain trusted for 1 year (default duration)
- Security Impact: Reduces authentication friction for trusted devices
- Admin Control: Can be disabled to prevent browser remembering
š² smsOtp
- Function: Controls SMS OTP availability for authentication
- When Enabled: SMS OTP appears as Level 2 authenticator option
- Prerequisites: User must have registered mobile number
- User Experience: Users receive 6-digit codes via text message
- Admin Control: Can be disabled to remove SMS option entirely
š§ emailOtp
- Function: Controls Email OTP availability for authentication
- When Enabled: Email OTP appears as Level 2 authenticator option
- Prerequisites: User must have registered email address
- User Experience: Users receive 6-digit codes via email
- Admin Control: Can be disabled to remove email option entirely
š alwaysAskForPassword
- Function: Forces password requirement regardless of other factors
- When Enabled: All users must enter password during login
- User Experience: Both username and password fields displayed
- Security Impact: Ensures password-based first factor for all authentications
- Use Case: Organizations requiring mandatory password verification
š Authentication Factor Control Matrix
| Authentication Factor | Hard-Coded | Configurable | Admin Override |
|---|---|---|---|
| š REL-IDverify Push Notification | ā Always Available | ā Cannot Disable | ā No Control |
| š± Time-based OTP (Mobile App) | ā Always Available | ā Cannot Disable | ā No Control |
| š Saved Browser (rememberMe) | ā Optional | ā Configurable | ā Full Control |
| š Password (alwaysAskForPassword) | ā Optional | ā Configurable | ā Full Control |
| š² SMS-based OTP (smsOtp) | ā Optional | ā Configurable | ā Full Control |
| š§ Email-based OTP (emailOtp) | ā Optional | ā Configurable | ā Full Control |
šÆ Configuration Impact on User Experience
When rememberMe = true
- ā "Remember Me" checkbox visible during login
- ā Users can save browsers for future quick access
- ā Account chooser appears on trusted browsers
- ā Reduced authentication steps for returning users
When rememberMe = false
- ā No browser remembering option available
- ā Users must complete full authentication every time
- ā Higher security through mandatory factor verification
- ā Increased authentication friction
When smsOtp = true
- ā SMS OTP available as second factor option
- ā Users can register mobile numbers
- ā Text message delivery for authentication codes
- ā Works with any SMS-capable mobile phone
When smsOtp = false
- ā SMS OTP not available during authentication
- ā Users cannot use mobile numbers for verification
- ā SMS-based account recovery may be limited
- ā Eliminates SMS delivery dependencies
When emailOtp = true
- ā Email OTP available as second factor option
- ā Users can register email addresses
- ā Email delivery for authentication codes
- ā Works with any email account
When emailOtp = false
- ā Email OTP not available during authentication
- ā Users cannot use email addresses for verification
- ā Email-based account recovery may be limited
- ā Eliminates email delivery dependencies
When alwaysAskForPassword = true
- ā Password required for all users
- ā Both username and password fields shown
- ā Consistent authentication experience
- ā Users without passwords cannot authenticate
When alwaysAskForPassword = false
- ā Password optional based on user setup
- ā Username-only entry for some users
- ā Flexible authentication paths
- ā Mobile-first user experience possible
Updated 4 months ago
