Hi,
My question is. Using the internal_auth method, how do I "login" a user into his account and associate that with the current active session or a newly created session?
I am new to much of this and am having a hard time understanding what needs to be done to simply have a client login to an existing ejabberd account. I am trying to build webbased modules. Currently I have pages being published and have registered accounts. I have setup http_bind and http_polling. It appears they start the sessions.
It is a problem figuring out how much of the various "session" intiation and "authorization" stanza exchanges have already been implimented in the various "mod_make_ejabberd_do_stuff" plugins and core modules. This is a particular area where I would like to integrate my module into ejabberd gracefully not hacked. To this point, trying to figure things out by analyzing the API and tracing through functionality is daunting. I need HELP.
It seems very few people outside of ProcessOne have gained an understanding of how to develop modules that integrate nicely with ejabberd. Hey maybe I can come work for you guys for free so I can learn ejabberd.
All kidding aside (or not), I would appreciate any help. I want to dream about a different problem this one is getting very old.
Thank You
Some general sentences
> how do I "login" a user into his account... what needs to be done to simply have a client login to an existing ejabberd account
To login a XMPP client in a XMPP server, follow the XMPP protocol:
> Using the internal_auth method,
ejabberd allows the administrator to store the account passwords in different places: internal DB, PAM service, LDAP server, ODBC DB...
XMPP clients don't care what storage method did the admin configure in the XMPP server.
> integrate my module into ejabberd gracefully not hacked.
If you implement a client following XMPP protocol, you don't need to modify ejabberd code.