User Registration & Verification
Step-by-step for user sign-up and email verification using Basic Authentication.
This workflow covers creating a user account with email/password and verifying the email address before allowing login.
Prerequisites
Users table in the helper file with fields for:
email,passwordHash,isVerified,isEnabled, and timestampsEmail delivery configured in
onAuthNotifier(server-side) for verification messages
Workflow
User submits the registration form
Run
authRegisteractionHelper file creates the user (password stored as a one-way hash)
System sends verification email with a time-bound verification link
User clicks the link and lands on a verification page
Run
authVerifyaction on page load to confirm the tokenMark the user record as verified (
isVerified = True)Optionally sign the user in or redirect to login
Page Actions
Registration page:
authRegisterVerification page:
authVerify(recommended to run in an onFormLoad named action)Optional resend-verification UI:
authResend(requiresemail)
Hooks (FileMaker)
onRegistration: optional post-registration business logiconAuthNotifier: send verification email and any admin notifications
Data Considerations
Verification tokens should be treated as secrets; avoid logging or storing them in cleartext
Verification tokens should be time-bound and single-use
Practical Notes
Registration pages must provide
emailandpasswordin the page model before runningauthRegisterIf you want a second "confirm password" field, use a custom validator to compare
passwordandpassword2Authentication feedback can be shown with
model.authMessage, or more robustly withmodel.authMessageCodeandmodel.authMessageTypeVerification pages usually run
authVerifyautomatically inonFormLoadThe verification action reads the token from the URL; you generally do not need to parse it manually
Users must still be enabled (
isEnabled = true) to sign in after verification
Related Pages
Last updated
Was this helpful?