Configuring instant messaging in Zarafa WebApp - Revision history

Admin at 12:07, 31 August 2012

2012-08-31T12:07:51Z

← Older revision		Revision as of 12:07, 31 August 2012
Line 27:		Line 27:

	The jabber server has to enabled with the http binding stuff.		The jabber server has to enabled with the http binding stuff.
		+	To use the http bind, the following has be available in the module section of the ejabber.cfg file.
		+
		+	{mod_http_bind, []},

	Restart apache to make the changes active.		Restart apache to make the changes active.

Admin at 18:52, 12 April 2012

2012-04-12T18:52:51Z

← Older revision		Revision as of 18:52, 12 April 2012
Line 51:		Line 51:
	mv ejabberd-extauth.php /usr/local/bin/jabberauth.php		mv ejabberd-extauth.php /usr/local/bin/jabberauth.php
	chmod 775 /usr/local/bin/jabberauth.php		chmod 775 /usr/local/bin/jabberauth.php
		+
		+	When running the WebApp on a different server than the ejabberd, change the webapp url in the following line in the auth script:
		+
		+	$auth->zarafa_urls = array("http://<ip-address>/webapp");

	Now the jabber client should be logged in, when you login to the webapp.		Now the jabber client should be logged in, when you login to the webapp.
	It's required that the webapp loginname is the same as the jabber loginname, otherwise it will fail.		It's required that the webapp loginname is the same as the jabber loginname, otherwise it will fail.

Milo at 18:18, 7 March 2012

2012-03-07T18:18:45Z

← Older revision		Revision as of 18:18, 7 March 2012
Line 23:		Line 23:
	Include in the /etc/apache2/sites-enabled/zarafa-webapp the following 2 lines:		Include in the /etc/apache2/sites-enabled/zarafa-webapp the following 2 lines:

-	ProxyPass /http-bind http://jabber.example.com:~~7070~~/http-bind/	+	ProxyPass /http-bind http://jabber.example.com:5280/http-bind/
-	ProxyPassReverse /http-bind http://jabber.example.com:~~7070~~/http-bind/	+	ProxyPassReverse /http-bind http://jabber.example.com:5280/http-bind/

	The jabber server has to enabled with the http binding stuff.		The jabber server has to enabled with the http binding stuff.
Line 48:		Line 48:

	Download the authentication script from https://community.zarafa.com/pg/plugins/project/6450/developer/milo/zarafa-webapp-ejabberd-authentication-script and place it in /usr/local/bin/jabberauth.php. Make sure php-cli is installed and the script is executable from the commandline.		Download the authentication script from https://community.zarafa.com/pg/plugins/project/6450/developer/milo/zarafa-webapp-ejabberd-authentication-script and place it in /usr/local/bin/jabberauth.php. Make sure php-cli is installed and the script is executable from the commandline.
-		+
		+	mv ejabberd-extauth.php /usr/local/bin/jabberauth.php
	chmod 775 /usr/local/bin/jabberauth.php		chmod 775 /usr/local/bin/jabberauth.php

	Now the jabber client should be logged in, when you login to the webapp.		Now the jabber client should be logged in, when you login to the webapp.
	It's required that the webapp loginname is the same as the jabber loginname, otherwise it will fail.		It's required that the webapp loginname is the same as the jabber loginname, otherwise it will fail.

Admin at 09:35, 4 March 2012

2012-03-04T09:35:19Z

← Older revision		Revision as of 09:35, 4 March 2012
Line 47:		Line 47:
	The default authentication can still be ldap, but an extra authentication will done over the external script jabberauth.php.		The default authentication can still be ldap, but an extra authentication will done over the external script jabberauth.php.

-	Download the authentication script from https://community.zarafa.com/pg/plugins/project/6450/developer/milo/zarafa-webapp-ejabberd-authentication-script and place it in /usr/local/bin/jabberauth.php. Make sure the script is executable from the commandline.	+	Download the authentication script from https://community.zarafa.com/pg/plugins/project/6450/developer/milo/zarafa-webapp-ejabberd-authentication-script and place it in /usr/local/bin/jabberauth.php. Make sure php-cli is installed and the script is executable from the commandline.

-	chmod ~~755~~ /usr/local/bin/jabberauth.php	+	chmod 775 /usr/local/bin/jabberauth.php

	Now the jabber client should be logged in, when you login to the webapp.		Now the jabber client should be logged in, when you login to the webapp.
	It's required that the webapp loginname is the same as the jabber loginname, otherwise it will fail.		It's required that the webapp loginname is the same as the jabber loginname, otherwise it will fail.

Admin at 13:25, 20 December 2011

2011-12-20T13:25:31Z

← Older revision		Revision as of 13:25, 20 December 2011
Line 5:		Line 5:

	This howto describes how the instant messaging plugin can be integrated with an ejabberd server.		This howto describes how the instant messaging plugin can be integrated with an ejabberd server.
		+	This article will not describe the installation and configuration steps of ejabberd. For more information about these steps, please check http://www.ejabberd.im/tutorials.

Admin at 13:22, 20 December 2011

2011-12-20T13:22:55Z

← Older revision		Revision as of 13:22, 20 December 2011
Line 22:		Line 22:
	Include in the /etc/apache2/sites-enabled/zarafa-webapp the following 2 lines:		Include in the /etc/apache2/sites-enabled/zarafa-webapp the following 2 lines:

-	ProxyPass /http-bind http://jabber.~~zarafa~~.com:7070/http-bind/	+	ProxyPass /http-bind http://jabber.example.com:7070/http-bind/
-	ProxyPassReverse /http-bind http://jabber.~~zarafa~~.com:7070/http-bind/	+	ProxyPassReverse /http-bind http://jabber.example.com:7070/http-bind/

	The jabber server has to enabled with the http binding stuff.		The jabber server has to enabled with the http binding stuff.
Line 46:		Line 46:
	The default authentication can still be ldap, but an extra authentication will done over the external script jabberauth.php.		The default authentication can still be ldap, but an extra authentication will done over the external script jabberauth.php.

-	Download the authentication script from ... and place it in /usr/local/bin/jabberauth.php.	+	Download the authentication script from https://community.zarafa.com/pg/plugins/project/6450/developer/milo/zarafa-webapp-ejabberd-authentication-script and place it in /usr/local/bin/jabberauth.php. Make sure the script is executable from the commandline.
-	Make sure the script is executable from the commandline.	+

	chmod 755 /usr/local/bin/jabberauth.php		chmod 755 /usr/local/bin/jabberauth.php

	Now the jabber client should be logged in, when you login to the webapp.		Now the jabber client should be logged in, when you login to the webapp.
-	It's ~~also~~ required that the webapp loginname is the same as the jabber loginname, otherwise it will fail.	+	It's required that the webapp loginname is the same as the jabber loginname, otherwise it will fail.

Admin at 13:07, 20 December 2011

2011-12-20T13:07:24Z

← Older revision		Revision as of 13:07, 20 December 2011
Line 41:		Line 41:
	Please add to the ejabber.cfg this lines:		Please add to the ejabber.cfg this lines:

-	{auth_method, \[ldap, external\]}	+	{auth_method, \[ldap, external\]}
-	{extauth_program, "/usr/local/bin/jabberauth.php"}	+	{extauth_program, "/usr/local/bin/jabberauth.php"}

	The default authentication can still be ldap, but an extra authentication will done over the external script jabberauth.php.		The default authentication can still be ldap, but an extra authentication will done over the external script jabberauth.php.

Admin at 13:07, 20 December 2011

2011-12-20T13:07:01Z

← Older revision		Revision as of 13:07, 20 December 2011
Line 29:		Line 29:
	Restart apache to make the changes active.		Restart apache to make the changes active.

-	To verify if the changes are active, please go to http://servername/http-bind .	+	To verify if the changes are active, please go to http://servername/http-bind.
-	This should redirect you to the ejabberd http-bind page. If this doesn't happen, please check if proxy passing is enabled in /etc/apache2/mod-enabled/proxy.conf.	+	This should redirect you to the ejabberd http-bind page.
-	ejabberd configuration	+	If this doesn't happen, please check if proxy passing is enabled in
		+
		+	/etc/apache2/mod-enabled/proxy.conf.
		+
		+
		+	== ejabberd configuration ==

	For the ejabberd setup the authentication method has to be extended with a custom script.		For the ejabberd setup the authentication method has to be extended with a custom script.

Admin: Created page with "The Zarafa WebApp includes a instant messaging plugin from revision 31187. The instant messaging plugin allow you to see the presence of your colleagues and start a chat conversa..."

2011-12-20T13:06:15Z

Created page with "The Zarafa WebApp includes a instant messaging plugin from revision 31187. The instant messaging plugin allow you to see the presence of your colleagues and start a chat conversa..."

New page

The Zarafa WebApp includes a instant messaging plugin from revision 31187.
The instant messaging plugin allow you to see the presence of your colleagues and start a chat conversation with them.

The instant messaging has to be integrated with an existing XMPP/Jabber server.

This howto describes how the instant messaging plugin can be integrated with an ejabberd server.

== WebApp configuration ==

The instant messaging (xmpp) plugin is by default available in the WebApp plugins directory.
To configure the xmpp plugin insert the jabber domain in the option PLUGIN_XMPP_CONNECT_DOMAIN in the config.php in the xmpp plugin directory.

There is at the moment no way of authenticating the user from the jabber client itself, this has to be done at the webapp login session.

== Apache configuration ==

The jabber webapp client is using the http-bind method for realtime notifications.
To support this, the Apache configuration has proxy some http-bind urls.

Include in the /etc/apache2/sites-enabled/zarafa-webapp the following 2 lines:

ProxyPass /http-bind http://jabber.zarafa.com:7070/http-bind/
ProxyPassReverse /http-bind http://jabber.zarafa.com:7070/http-bind/

The jabber server has to enabled with the http binding stuff.

Restart apache to make the changes active.

To verify if the changes are active, please go to http://servername/http-bind .
This should redirect you to the ejabberd http-bind page. If this doesn't happen, please check if proxy passing is enabled in /etc/apache2/mod-enabled/proxy.conf.
ejabberd configuration

For the ejabberd setup the authentication method has to be extended with a custom script.
Please add to the ejabber.cfg this lines:

{auth_method, \[ldap, external\]}
{extauth_program, "/usr/local/bin/jabberauth.php"}

The default authentication can still be ldap, but an extra authentication will done over the external script jabberauth.php.

Download the authentication script from ... and place it in /usr/local/bin/jabberauth.php.
Make sure the script is executable from the commandline.

chmod 755 /usr/local/bin/jabberauth.php

Now the jabber client should be logged in, when you login to the webapp.
It's also required that the webapp loginname is the same as the jabber loginname, otherwise it will fail.