fix: Use correct bcrypt hash for demo123 password

Browse Source

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

...

This commit is contained in:

Warren

2026-05-17 00:43:34 +08:00

parent a5169b1989

commit 990311318d

1 changed files with 0 additions and 0 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

BIN

data/auth.sqlite

Binary file not shown.