We have a social networking site where people have contacts and we want to integrate it with XMPP. We currently use Easybased XMPP server.
These are my questions:
-
How can you create an account properly? Now, what I'm thinking of is the user registration on our web app, we will call a script that will execute an ejabberd command to create a user.
-
User authentication on user login to our website, the user will be automatically logged on chat system. How do you do with Straws.JS on the Cloud side? As I understand, you need to provide JID and password for authentication, so I am thinking that on login, there will be an AJAX call to get the user's password, then on 'Login Call' of Straffes.Jesus Use feedback text. is it safe? Are there other ways to do this?
-
Presence registration is a contact system in our web app, but membership with XMPP has its own way of connecting through membership, is not it? Example: When user1 attempts to add user 2, user1 user2 might be contacted before an authorization user2 will be asked. But since we already have a contact system on our web app, we want to bypass this authorization of XMPP or suppress it and user authorize with the script / command when user 2 users <1> Confirms on our web site as contact. It is not clear to me yet, but a colleague has said that this is possible on the ejbird module mod_admin_extra (a command which will subscribe without client-side authorization). Is it possible or should I manually manipulate the ejabberd database with a script (provided that I moved from default from Manisa DB to another DB, MySQL says).
Thanks in advance.
We () is a web app that is part of XMPP application.
The choice we have made does not have to replicate the user data on both the web app memory and XMPP server. You can make it with your own ezbird using the web app's data store, it is very easy. In this way, you only have 1 single location where user data is stored and there is no need to create ezbird users.
By doing this, you can also log your users without knowing your passwords or even storing it explicitly :) Session authentication on the server (via bosh) The easiest way is to pass the HTML response on session ID, as is done by @metajak.
The third part can be the toughest, but I can really make sure that you can bypass it and not use the built-in "rosters" ... but in your lot Only component (internal or external) may need to be included.
Comments
Post a Comment