The password is likely left empty for security reasons. After analyzing the code execution flow, the solution is as follows. I use MD5 encryption for the password:
UCenter backend notification program after changing the password:
ucenter.kchmc.net/control/admin/user.php
//$_ENV[‘note’]->add(‘updatepw’, ‘username=’.urlencode($username).’&password=’);
$_ENV[‘note’]->add(‘updatepw’, ‘username=’.urlencode($username).’&password=’.md5($orgpassword));
UCenter notification program:
ucenter.kchmc.net/control/user.php
//$_ENV[‘note’]->add(‘updatepw’, ‘username=’.urlencode($username).’&password=’);
$_ENV[‘note’]->add(‘updatepw’, ‘username=’.urlencode($username).’&password=’.md5($newpw));
If the password is modified in Application A, and the other applications to be notified use independent user databases, you need to modify the corresponding code in the UCenter client (uc_client):
kchmc.net/phpsso_server/api/uc_client/control/user.php
//$_ENV[‘note’]->add(‘updatepw’, ‘username=’.urlencode($username).’&password=’);
$_ENV[‘note’]->add(‘updatepw’, ‘username=’.urlencode($username).’&password=’.md5($newpw));
At this point, kchmc.net and ucenter.kchmc.net may have already updated the password, but other applications might not have been notified yet, or the notification may have failed. One solution now is to simply wait, or manually trigger the notification again directly from the notification list on ucenter.kchmc.net!