ejabberd - Comments for "Anybody can help me with the log-in issue? URGENT"

Re: my concern

sander — Tue, 04 Apr 2006 09:17:35 +0000

smarthunter wrote:

2. Ideally, we do hope to use personal instant messaging chats along with group chats. In this case, do you happen to have any solution to help us?

MUCkl also allows private chat sessions with people in the room. The only drawback is that this is not implemented that userfriendly (and maybe it is not what you want). Read also this blog post if you want to improve MUCkl.

Quote:

4. Do you have any comments about the difference between ejabberd and wildfire? We believe the performance of ejabberd is better than wildfire since it is developed with erlang. But we are wondering if we are able to develop the custom scripts for external auth with JAVA OR JSP.

The Open-source XMPP server comparison chart can be a good start.

You also might be interesting to read Erlang for C, C++ and Java Programmers to get a brief introduction into Erlang.

Re: my concern

mfoss — Tue, 04 Apr 2006 08:24:38 +0000

smarthunter wrote:

1. In terms of extauth and custom script, we are familiar with JAVA and JSP (not those existing scripts writen with Php,etc), is that possible to write the custom script with java or jsp? Or maybe I have to migrate to Wildfire( previous jive messenger)?

It should be perfectly capable, why not? Think about it: if languages as different as C, Perl and PHP are capable, why Java, JSP, Ruby, Tcl, Javascript... would not be?

Unfortunately, since extauth is barely documented, you will have to learn it looking at the current examples. Once you write your script in a new language, consider allowing me to publish it on the page.

smarthunter wrote:

2. Ideally, we do hope to use personal instant messaging chats along with group chats. In this case, do you happen to have any solution to help us?

Using the proposed solution MUCkl+custom URL does not remove the ability to use standard Jabber clients or JWChat to do a standard login (introducing username and password).

If you mean that the autologin client must be able to do personal chats, not only chatrooms, then MUCkl is not interesting and you should go back to JWChat. The autologin may be possible with JWChat too, but the autoopen_chatroom doesn't seem as easy.

Another alternative are the Java applet clients (Jeti, JBother...). With your knowledge in Java, I guess you are capable of hacking one of them to work as you want (autologin, autoopen chatroom...).

smarthunter wrote:

3. I am not sure whether the MUCKL is stable as jwchat does. Can you give me some hints?

No idea, I only tried MUCkl as user, not admin.

smarthunter wrote:

What I know about wildfire is what people say on forums or blogs so I can't say anything you don't already know.

my concern

smarthunter — Tue, 04 Apr 2006 04:22:11 +0000

Thank you for analysis that is correct. But I still have some concerns:

2. Ideally, we do hope to use personal instant messaging chats along with group chats. In this case, do you happen to have any solution to help us?

3. I am not sure whether the MUCKL is stable as jwchat does. Can you give me some hints?

Thank you again for your help.

Proposed solution with MUCkl

mfoss — Mon, 03 Apr 2006 17:57:24 +0000

If I understood correctly, your post includes three questions, different but related:

Usernames and passwords are not stored by ejabberd itself, they are stored on an external place (MySQL in this case). This probably requires to use extauth + custom script.
Since your users access the Jabber client (JWChat) from a personal web, they already introduced their personal username and password on that CMS. You want to place a link on their page: 'Join now the chatroom of my group', that opens JWChat and automatically logins, without asking username and password to the user.
Since each person is assigned to only one group, you want that when JWChat is opened, it automatically joins the corresponding chatroom.

If you only plan to use chatroom chats, not personal instant messaging chats, maybe you prefer MUCkl over JWChat. It's based on the same source code, by the same author and it's similar to configure.

The idea is that, on the personal page that your user sees after entering his username and password on the CMS, you show him a custom HTML link. That URL points to MUCkl and includes the username and the chatroom name that should be used. Since those links are made by your CMS, and are personal to each user, only ppl with the correct username and password will access them, right? (problem 1 solved). This way your user automatically joins the correct chatroom (problem 3 solved). Since MUCkl does not require password to login on ejabberd, your users will not be asked about it (problem 2 solved).

I'm not sure if that MUCkl customization is possible, so you will have to find it yourself. If it seems possible but you find problems, maybe MUCkl author is able to provide commercial support for his software.