On IGCN files the password mode is chosen in the DataServer and the database column must be of the matching type. If they do not match, nobody can log in.
- Close the whole server and back up MuOnline (and Me_MuOnline if you use it):
BACKUP DATABASE [MuOnline] TO DISK = N'C:\MUBackup\MuOnline_before_md5.bak' WITH INIT;- Open
1. DataServer\IGCDS.ini, section [JoinServer], keyPasswordEncryptType:
- 0 = no MD5, memb__pwd varchar(20)
- 1 = WZ_MD5, memb__pwd binary(16), only on x86 (32 bit) SQL Server, needs WZ_MD5_MOD.dll
- 2 = IGC_MD5, memb__pwd varchar(32), md5 of the password as PHP md5() makes it
- 3 = SHA256, memb__pwd binary(32), uses PasswordEncryptSalt
- Check what your database really has:
SELECT DATA_TYPE, CHARACTER_MAXIMUM_LENGTH FROM INFORMATION_SCHEMA.COLUMNS
WHERE TABLE_NAME = 'MEMB_INFO' AND COLUMN_NAME = 'memb__pwd';- For a new server use the matching script from
Database\1. Full Scripts: MuOnline_MD5.sql (binary(16)) or MuOnline_without_MD5.sql (varchar(20)), and the same pair for Me_MuOnline. The two files differ only in that one column. - Accounts saved in the old form do not log in after a switch: reset their passwords in the new form (see "IGCN: set a new password for one account in SQL") and make the website use the same mode (WebEngine: none / wzmd5 / phpmd5 / sha256).
Source: IGCN Season 16 and 17 server files, 1. DataServer/IGCDS.ini ([JoinServer] PasswordEncryptType block) and Database/1. Full Scripts (MuOnline_MD5.sql, MuOnline_without_MD5.sql, Me_MuOnline pair); the IGCN 18.2.2.13 suite ships the same files.