- Sign in and OAuth provider actions
- Registration and multi-step navigation
- Password visibility and strength labels
- Password reset request and new password form
- Email verification
- Two-factor authentication
- Logout confirmation
Localized fields
The global Content language selector at the top of LucentUI Editor controls the auth fields. Fill English first, then switch to each enabled Paymenter language. Dynamic placeholders such as:provider are part of the message contract. Preserve them
in translations so the runtime provider name remains visible.
Error states
Laravel and Paymenter validation messages remain authoritative. LucentUI styles failed authentication, password mismatch, and form-level errors as danger content while keeping field-level guidance readable in light and dark mode.Test matrix
1
Test failed sign-in
Confirm the error is red, announced near the form, and does not reveal account details.
2
Test registration validation
Submit missing and mismatched values, move backward and forward, and check mobile layout.
3
Test password recovery
Verify request, token reset, strength labels, visibility toggles, and completion state.
4
Test email verification and 2FA
Check code entry, resend actions, invalid-code errors, and navigation back to sign-in.
5
Test logout
Confirm that logout opens the LucentUI confirmation modal and cancel keeps the session active.