Warren
990311318d
fix: Use correct bcrypt hash for demo123 password
Critical fix:
- Previous hash was for admin123, not demo123
- Generated fresh bcrypt hash specifically for 'demo123'
- Verified hash with bcrypt::verify() = true ✅
Database updates:
- PostgreSQL users.password (demo) - 60 chars ✅
- SQLite sftpgo_users.password_hash (demo) - 60 chars ✅
- PostgreSQL admins.password (admin) - 60 chars ✅
- SQLite sftpgo_admins.password_hash (admin) - 60 chars ✅
Test result:
✅ demo/demo123 login returns token
✅ admin/demo123 login returns token
Password (unified): demo123
Test users:
- File Tree: demo / demo123
- Settings: admin / demo123
Files:
- data/auth.sqlite
2026-05-17 00:43:34 +08:00
..
2026-05-16 15:37:37 +08:00
2026-05-16 15:37:37 +08:00
2026-05-17 00:43:34 +08:00
2026-05-16 20:47:28 +08:00