contentbox-boxlang-two-factor-authentication
Use this skill when implementing or customizing ContentBox two-factor authentication providers, trusted device flows, enrollment/verification UX, enforcement policies, and provider lifecycle handling.
ContentBox Two-Factor Authentication (BoxLang)
Implement and extend two-factor authentication (2FA) in ContentBox CMS using BoxLang. ContentBox provides a pluggable 2FA system with provider interfaces, trusted device support, and global enforcement.
2FA Architecture
The 2FA system lives at modules/contentbox/models/security/twofactor/:
| Component | File | Purpose |
|---|---|---|
| Interface | ITwoFactorProvider.cfc | Contract all 2FA providers must implement |
| Base Class | BaseTwoFactorProvider.cfc | Base class with injected services |
| Service | TwoFactorService.cfc | Provider registry and orchestration |
TwoFactorService
The central service manages 2FA providers and settings:
property name="twoFactorService" inject="twoFactorService@contentbox"
// Provider management
twoFactorService.registerProvider( provider )
twoFactorService.unRegisterProvider( name )
twoFactorService.getRegisteredProviders()
twoFactorService.getRegisteredProvidersWithDisplayNames()
twoFactorService.getProvider( name )
// Settings
twoFactorService.isForceTwoFactorAuth()
twoFactorService.getDefaultProvider()
twoFactorService.getDefaultProviderObject()
twoFactorService.getTrustedDeviceTimespan()
2FA Settings
Stored in the cb_setting table:
| Setting Key | Description |
|---|---|
cb_security_2factorAuth_force | Force global 2FA enrollment (true/false) |
cb_security_2factorAuth_provider | Default provider name |
cb_security_2factorAuth_trusted_days | Trusted device cookie duration (days) |
Trusted Device Cookie
variables.TRUSTED_DEVICE_COOKIE = "contentbox_2factor_device"
When allowTrustedDevice() returns true, a cookie is set. If the user logs in from the same device within the trusted timespan, 2FA validation is skipped.
ITwoFactorProvider Interface
All 2FA providers must implement this interface:
interface {
/**
* Get the internal name of a provider, used for registration, internal naming and more.
*/
function getName()
/**
* Get the display name for the provider. Used in all UI screens.
*/
function getDisplayName()
/**
* Returns HTML to display to the user for required two-factor fields.
*/
function getAuthorSetupForm( required author )
/**
* Get the display help for the provider. Used in the UI setup screens for the author.
*/
function getAuthorSetupHelp( required author )
/**
* Get the verification help for the provider. Used in the UI verification screen.
*/
function getVerificationHelp()
/**
* If true, ContentBox will set a tracking cookie for the user's browser.
* If the user logs in from the same device within the trusted timespan,
* no two-factor authentication validation will occur.
*/
boolean function allowTrustedDevice()
/**
* Send a challenge via the 2 factor auth implementation.
*
* @author The author to challenge
* @return struct:{ error:boolean, messages=string }
*/
struct function sendChallenge( required author )
/**
* Verify a challenge for the specific user.
*
* @code The verification code
* @author The author to verify challenge
* @return struct:{ error:boolean, messages:string }
*/
struct function verifyChallenge( required string code, required author )
/**
* Called once a two factor challenge is accepted and valid.
* The user has completed validation and will be logged in.
*
* @code The verification code
* @author The author to verify challenge
*/
function finalize( required string code, required author )
}
Creating a Custom 2FA Provider
Base Provider
Extend BaseTwoFactorProvider for auto-injected services:
// models/security/MyTOTPProvider.bx
component
extends="contentbox.models.security.twofactor.BaseTwoFactorProvider"
singleton
implements="contentbox.models.security.twofactor.ITwoFactorProvider"
{
function init(){
return this
}
function getName(){
return "mytotp"
}
function getDisplayName(){
return "My TOTP Authenticator"
}
function getAuthorSetupForm( required author ){
return "
<div class='form-group'>
<label>Secret Key</label>
<input type='text' name='totp_secret' class='form-control'
value='#{author.getTwoFactorSecret() ?: ''}#'>
</div>
"
}
function getAuthorSetupHelp( required author ){
return "<p>Scan the QR code with your authenticator app.</p>"
}
function getVerificationHelp(){
return "<p>Enter the 6-digit code from your authenticator app.</p>"
}
boolean function allowTrustedDevice(){
return true
}
struct function sendChallenge( required author ){
// Send the challenge (e.g., generate TOTP, send SMS, etc.)
return { error : false, messages : "Challenge sent successfully." }
}
struct function verifyChallenge( required string code, required author ){
// Verify the code
isValid = verifyTOTP( arguments.code, arguments.author.getTwoFactorSecret() )
if( isValid ){
return { error : false, messages : "Code verified." }
} else {
return { error : true, messages : "Invalid code. Please try again." }
}
}
function finalize( required string code, required author ){
// Called after successful validation
log.info( "2FA finalized for author: #{author.getUsername()}#" )
}
// Private helper
function verifyTOTP( required string code, required string secret ){
// TOTP verification logic
return true
}
}
Registering a 2FA Provider
Register your provider in your module's onLoad():
function onLoad(){
twoFactorService = wirebox.getInstance( "twoFactorService@contentbox" )
twoFactorService.registerProvider(
wirebox.getInstance( "MyTOTPProvider@mymodule" )
)
}
2FA Enforcement
Global Enforcement
The CheckForForceTwoFactorEnrollment interceptor enforces 2FA globally:
- Runs on
preProcessfor admin requests - Excludes security module events (login, logout, password reset)
- Redirects unenrolled users to
cbadmin/security/twofactorEnrollment/forceEnrollment
Provider Change Handling
The UnenrollTwoFactorOnProviderChange interceptor handles provider changes:
- When the default 2FA provider is changed in settings
- Unenrolls all users from 2FA (they must re-enroll with the new provider)
Author 2FA Properties
The Author entity stores 2FA-related data:
// Author entity 2FA properties
property name="twoFactorEnabled" ormtype="boolean" default="false"
property name="twoFactorSecret" ormtype="string" length="500"
property name="twoFactorProvider" ormtype="string" length="100"
Checking 2FA Status
property name="authorService" inject="authorService@contentbox"
property name="twoFactorService" inject="twoFactorService@contentbox"
// Check if global 2FA is forced
if( twoFactorService.isForceTwoFactorAuth() ){
// All users must enroll
}
// Check if a specific author has 2FA enabled
if( author.getTwoFactorEnabled() ){
// Author has 2FA enabled
}
// Get the default provider
provider = twoFactorService.getDefaultProviderObject()
Built-in 2FA Providers
ContentBox ships with these providers:
| Provider | Description |
|---|---|
| TOTP | Time-based One-Time Password (RFC 6238) โ works with Google Authenticator, Authy, etc. |
Best Practices
- Implement
ITwoFactorProviderโ all methods are required - Extend
BaseTwoFactorProviderโ provides DI forlog,settingService,securityService,siteService,renderer,CBHelper - Return proper structs โ
sendChallenge()andverifyChallenge()must return{ error, messages } - Use
singletonscope โ providers are instantiated once - Register in
onLoad()โ register providers after module configuration - Support trusted devices โ implement
allowTrustedDevice()for better UX - Store secrets securely โ use encryption for sensitive data
- Provide clear help text โ
getAuthorSetupHelp()andgetVerificationHelp()guide users - Handle errors gracefully โ return meaningful error messages
- Test enrollment flow โ verify the full enrollment and verification cycle
Engine Compatibility
This skill targets BoxLang engine. For CFML-specific syntax (Lucee 5+, Adobe ColdFusion 2018+), see the CFML variant of this skill.
Key BoxLang advantages:
- Cleaner script syntax without
<cfcomponent>/<cffunction>tags - No parentheses needed for zero-argument function calls
#{...}#for inline expression output in.bxtemplates- Modern syntax:
?:null coalescing,?.safe navigation - Native support for modern data structures