So, you are using system PAM to authenticate users. So your C2S does not touch "authreg" table. It strange though, that you have anything in it.
Thank you, that is what I wanted to know. Yes, it is strange... Content of "active" table is managed by SM. It inserts rows on account registration normally or on user login if you have <autocreate/> option enabled. The <autocreate/> option is enbaled. This is great. I should be able to use the data in the active table in a script to get a list of all my users. Thanks very much. BTW I had heard not too long ago that the maintainer for jabberd2 had moved onto another project and jabberd to was no longer maintained. I would say that is not the case. Seems to me it is supported better than most. Are you planning to continuing working on jabberd2? -----Original Message----- From: Tomasz Sterna [mailto:[email protected]] Sent: Wednesday, March 17, 2010 10:54 AM Subject: RE: Jabberd2 MySQL data migration Dnia 2010-03-17, śro o godzinie 15:36 +0000, Leslie G. Seigneur pisze: > >So, if you intent to get JIDs of your users from DB, you should > better > >rely on "active" table. > > Good to know. Can you tell me by what mechanism the JIDs get entered > into the active table? > > --------------------- begin authreg ------------------------ > > <!-- Authentication/registration database configuration --> > <authreg> > <!-- Backend module to use --> > <module>pam</module> So, you are using system PAM to authenticate users. So your C2S does not touch "authreg" table. It strange though, that you have anything in it. Content of "active" table is managed by SM. It inserts rows on account registration normally or on user login if you have <autocreate/> option enabled. -- To unsubscribe send a mail to [email protected]
