Inconsistency with mysql stored procs

Submitted by Anonymous on Tue, 2010-07-27 00:43
::

I am working with the 5.0.x release of Tigase. I noticed that there is a script file for setting up the stored procedures in mysql. There is a couple for adding a user to the system. Problem is if I use the stored procedure the user doesn't seem to get added properly as I can't login with that user. If I create a user through an XMPP client then it works fine.

Upon further investigation I see that there is a password field within the tig_users table which is populated by the stored procedure but the Tigase server is actually using a "password" key within the tig_pairs table to authenticate.

Are the stored procedures still valid for a mysql data store? If so is there something I am missing when creating the user through the stored procedures? Why are those procedures there if they aren't being used by the server?

Thanks for any insight you can provide.

‹ Is there to override the Session Manager Authentication timer timeout? Access a roster out side of a session ›
Artur Hefczyc's picture

I hope this article explains

Submitted by Artur Hefczyc on Tue, 2010-07-27 06:29.

I hope this article explains everything. There are different authentication connectors possible and available for the Tigase server. Some of them use stored procedures, some of them don't and there is one which allows you to define own queries to retrieve user authentication data.
Apparently you are using authentication connector which keeps user password in tig_pairs table. I would recommend to use tigase-auth connector which uses stored procedures and keeps user password in tig_users table.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Post new comment

The content of this field is kept private and will not be shown publicly.