I have developed my own application according to the manual and can log on and exit synchronously. However, I found a problem during the test, when I directly modify A user's password on the ucserver management interface, the following occurs: User A's original password: 1231. the first time I changed the password to abc, I... you have developed your own applications according to the manual and can log on and exit simultaneously.
However, during the test, I found a problem. When I directly modify a user's password on the management interface of the uc server, this problem occurs first:
User A's original password: 123
1. The first time I changed the password to abc, I did not receive any notification of password change for my own apps.
2. The second time I changed my password to aaa, my self-developed application was notified of changing the password to abc.
3. The second time I changed my password to bbb, my self-developed application was notified to change my password to aaa ......
It is always a slow beat with changes. Ask what the problem is.
Reply content:
You have developed your own applications according to the manual and can log on and exit simultaneously.
However, during the test, I found a problem. When I directly modify a user's password on the management interface of the uc server, this problem occurs first:
User A's original password: 123
1. The first time I changed the password to abc, I did not receive any notification of password change for my own apps.
2. The second time I changed my password to aaa, my self-developed application was notified of changing the password to abc.
3. The second time I changed my password to bbb, my self-developed application was notified to change my password to aaa ......
It is always a slow beat with changes. Ask what the problem is.
When you change the password of uc, capture the packet and check whether the request has been sent to your application's uc. php.