📖 ~1 min read
Table of contents
Symptom & Impact
Multiple users are unexpectedly denied login, impacting normal operations and support workflows.
Environment & Reproduction
Common after policy changes in login.conf, PAM, or directory-synced accounts.
pw lockstat
loginctl || true
grep -R password /etc/pam.d
Root Cause Analysis
Conflicting password/lockout thresholds enforce stricter behavior than intended.
Quick Triage
Identify affected users and the active policy class.
pw usershow admin
cap_mkdb /etc/login.conf
last | head
Step-by-Step Diagnosis
Trace authentication path through PAM and login class definitions.
grep -n default /etc/login.conf
authctl test || true
tail -n 100 /var/log/auth.log

Solution – Primary Fix
Normalize policy values, rebuild capability database, and unlock accounts.
Still having issues? Our IT Consulting team can diagnose and resolve this for you. Get in touch for a free consultation.
vipw
cap_mkdb /etc/login.conf
pw unlock admin

Solution – Alternative Approaches
Adopt centralized identity policy with staged rollout and explicit exception classes.
Verification & Acceptance Criteria
Users authenticate normally under approved password and lockout policy.
su - admin
ssh admin@localhost true
Rollback Plan
Restore previous login.conf and PAM backups if new policy causes regressions.
cp /etc/login.conf.rollback /etc/login.conf
cap_mkdb /etc/login.conf
Prevention & Hardening
Review policy changes in change control and test against representative accounts first.
Related Errors & Cross-Refs
Often linked to sudo failures and SSH authentication confusion after lockouts.
Related tutorial: View the step-by-step tutorial for freebsd-15.
View all freebsd-15 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
login.conf(5), pam(8), and FreeBSD account policy documentation.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.