Update client cache failed!

Solution process:

Add the following method to phpsso_server/api/uc.php class uc_note:

//update client cache
function updateClient($get, $post) {
if(!api_updateClient) {
return api_return_forbidden;
}
$cacheFile = dirname(__file__)./uc_client/data/cache/settings.php;
$fp = fopen($cachefile,w);
$s = “<?php\r\n”;
$s .=$_cache[\’settings\’]=.var_export($post, true).”;\r\n”;
fwrite($fp, $s);
fclose($fp);
return api_return_succeed;
}

Update client cache success!

Check the PHPSSO_SERVER\API\UC_Client\Data\Cache\Settings.php file and find that the update has been successful:

settings.php has been updated successfully!

List of user tables in UCenter database

After modifying the user password in the A application, in the notification list of updating the user password, it is found that the password is empty!

Password is empty should be based on security considerations, the analysis code execution process, the solution is as follows, in Password I use MD5 encryption:

Notification program after ucenter changes the password in the background:
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 changed in the A application, and other applications that need to be notified use the independent user database, you need to modify the corresponding code of 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));

Notification form after updating the program!

Now it is possible that kchmc.net and ucenter.kchmc.net have updated the password, but other applications may not be notified, or The notification fails, and now one solution is to continue to wait, or manually operate the notification again in the ucenter.kchmc.net notification list!

In phpcms, the login prompts to log in successfully, check the source code, you can see that the synchronization js notification has been found

In phpcms, the exit prompt is successful 0, check the source code, you can see that the synchronization js notification code is 0

Analyze the code execution process:

1. kchmc.net/phpcms/modules/member/index.php

$SynLogoutstr = $this->client-> ps_member_synlogout();

2. kchmc.net/phpcms/modules/member/classes/client.class.php

Modified to be as follows:

/**
* Synchronized exit
* @param string $UID
* @return string javascript user sync exit js
*/
public function ps_member_synlogout() {
//return $this->_ps_send(synlogout, array());
return $this->_ps_send(synlogout, array(synlogout=>1));
}

3. kchmc.net/phpsso_server/phpcms/modules/phpsso/classes/phpsso.class.php

The reason is what is indicated in the red box:

If $this->data is empty, return 0

4. The revised result is as follows:

Quitting in phpcms prompts the exit successfully, check the source code, you can see that the synchronization js notification has been found

The backend user list of PC V9!

A membership form in the SSO of PC V9!

Add the application PHPSSO to the newly installed UC!

At this time, it prompts that the communication failed!

UCenter configuration in PHPSSO!

The application list in UC shows that the communication is successful!

Execute SQL and import member data in PHPSSO to UC!

Operate MemberFields in UC!

Link the member ID to the member ID in UC in PHPSSO!

To some extent, the execution is successful, and the member data in PHPSSO is synchronized to UC. Users who have previously registered in PHPCMS V9 can log in and activate in other UCs that should be registered!