We were using --auth-db=drupal on tigase.org . We stopped using drupal login some time ago. I tried to add an account for Daniel right from the database using TigAddUserPlainPW@. The user was created but couldn't login: not authorized. I then tried to use Pidgin to create the account. I was not successful registering the account, nor logging in with the user created directly until I changed @--auth-db=tigase-auth AND adding +jabber\:iq\:register to @sm-plugins@. I was then able to register and login with the account on both t2 and t6. I then verified on t2 and t6 that my own account could login and nothing was broken. Then Artur was having problems logging in some of his accounts. Turned out the accounts in question were connecting to t6 which I hadn't updated with the new register settings. Updated t6 and then login worked.
So one question is why do we now need jabber\:iq\:register in order to login?
One of Artur's accounts had it's password reset to @NULL@. Then it happened to Andrzej, Bartosz, and Wojciech. Didn't happen to me, didn't happen to Artur's other accounts, didn't happen to Daniel's account.
So the next question is why were passwords reset to @NULL@? Will it happen again?
Cannot be this was happening on t6 before the new settings were added because I logged in there and my password was not reset, 2 of Artur's 3 accounts logged in there and did not have password reset.
Bartosz MaĆkowski commented 9 years ago
I think that we not need jabber:iq:register to login. We need it only to register new account and to change password on existing account.
No idea why passwords was resetted. I have no idea how it could happend.
We were using
--auth-db=drupal
on tigase.org . We stopped using drupal login some time ago. I tried to add an account for Daniel right from the database usingTigAddUserPlainPW@. The user was created but couldn't login: not authorized. I then tried to use Pidgin to create the account. I was not successful registering the account, nor logging in with the user created directly until I changed @--auth-db=tigase-auth
AND adding+jabber\:iq\:register
to @sm-plugins@. I was then able to register and login with the account on both t2 and t6. I then verified on t2 and t6 that my own account could login and nothing was broken. Then Artur was having problems logging in some of his accounts. Turned out the accounts in question were connecting to t6 which I hadn't updated with the new register settings. Updated t6 and then login worked.So one question is why do we now need
jabber\:iq\:register
in order to login?One of Artur's accounts had it's password reset to @NULL@. Then it happened to Andrzej, Bartosz, and Wojciech. Didn't happen to me, didn't happen to Artur's other accounts, didn't happen to Daniel's account.
So the next question is why were passwords reset to @NULL@? Will it happen again?
Cannot be this was happening on t6 before the new settings were added because I logged in there and my password was not reset, 2 of Artur's 3 accounts logged in there and did not have password reset.