diff --git a/ChangeLog b/ChangeLog
index 0b32ba3a6..d270dfd19 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,10 @@
+2008-06-13 Badlop Probably the easiest way to install an ejabberd instant messaging server
+ Probably the easiest way to install an ejabberd instant messaging server
is using the binary installer published by Process-one.
The binary installers of released ejabberd versions
are available in the Process-one ejabberd downloads page:
http://www.process-one.net/en/ejabberd/downloads The installer will deploy and configure a full featured ejabberd
server and does not require any extra dependencies. In *nix systems, remember to set executable the binary installer before starting it. For example:
-
+
-
@@ -110,7 +117,8 @@ SPAN{width:20%; float:right; text-align:left; margin-left:auto;}
ejabberd Development Team Contents
-
-Chapter 2 Installing ejabberd
-2.1 Installing ejabberd with Binary Installer
Chapter 2 Installing ejabberd
+2.1 Installing ejabberd with Binary Installer
chmod +x ejabberd-2.0.0_1-linux-x86-installer.bin
- ./ejabberd-2.0.0_1-linux-x86-installer.bin
+
chmod +x ejabberd-2.0.0_1-linux-x86-installer.bin +./ejabberd-2.0.0_1-linux-x86-installer.bin
ejabberd can be started manually at any time, or automatically by the operating system at system boot time.
To start and stop ejabberd manually, use the desktop shortcuts created by the installer. @@ -314,29 +322,27 @@ and for example it doesn’t read the file ejabberdctl.cfg.
On a *nix copy ejabberd.init from the ’bin’ directory to something like /etc/init.d/ejabberd (depending on your distribution) and call /etc/inid.d/ejabberd start to start it.
The ejabberdctl administration script is included in the bin directory. Please refer to the section 4.1 for details about ejabberdctl, -and configurable options to fine tune the Erlang runtime system.
-Some Operating Systems provide a specific ejabberd package adapted to +and configurable options to fine tune the Erlang runtime system.
+Some Operating Systems provide a specific ejabberd package adapted to the system architecture and libraries. It usually also checks dependencies and performs basic configuration tasks like creating the initial administrator account. Some examples are Debian and Gentoo. Consult the resources provided by your Operating System for more information.
Usually those packages create a script like /etc/init.d/ejabberd -to start and stop ejabberd as a service at boot time.
-CEAN +to start and stop ejabberd as a service at boot time.
+CEAN (Comprehensive Erlang Archive Network) is a repository that hosts binary packages from many Erlang programs, including ejabberd and all its dependencies. The binaries are available for many different system architectures, so this is an alternative to the binary installer and Operating System’s ejabberd packages.
You will have to create your own ejabberd start script depending of how you handle your CEAN installation. The default ejabberdctl script is located -into ejabberd’s priv directory and can be used as an example.
-- +into ejabberd’s priv directory and can be used as an example.
+The canonical form for distribution of ejabberd stable releases is the source code package. Compiling ejabberd from source code is quite easy in *nix systems, -as long as your system have all the dependencies.
-- +as long as your system have all the dependencies.
+To compile ejabberd on a ‘Unix-like’ operating system, you need:
Released versions of ejabberd are available in the Process-one ejabberd downloads page: http://www.process-one.net/en/ejabberd/downloads
Alternatively, the latest development version can be retrieved from the Subversion repository using this command: -
svn co http://svn.process-one.net/ejabberd/trunk ejabberd --
svn co http://svn.process-one.net/ejabberd/trunk ejabberd ++
To compile ejabberd execute the commands: -
./configure - make +./configure +makeThe build configuration script provides several parameters. To get the full list run the command: -
./configure --help +./configure --helpSome options that you may be interested in modifying:
To install ejabberd in the destination directories, run the command: -
make install +make installNote that you may need to have administrative privileges in the system.
The files and directories created are, by default:
You can use the ejabberdctl command line administration script to start and stop ejabberd.
Usage example: -
$ ejabberdctl start +ejabberdctl start -$ ejabberdctl status +ejabberdctl status Node ejabberd@localhost is started. Status: started ejabberd is running -$ ejabberdctl stop +ejabberdctl stopPlease refer to the section 4.1 for details about ejabberdctl, -and configurable options to fine tune the Erlang runtime system.
-2.4.6 Specific Notes for BSD
- +and configurable options to fine tune the Erlang runtime system.
+2.4.6 Specific Notes for BSD
The command to compile ejabberd in BSD systems is: -
gmake --2.4.7 Specific Notes for Microsoft Windows
-Requirements
To compile ejabberd on a Microsoft Windows system, you need: +
gmake ++2.4.7 Specific Notes for Microsoft Windows
+Requirements
To compile ejabberd on a Microsoft Windows system, you need:
We assume that we will try to put as much library as possible into C:\sdk\
to make it easier to track what is install for ejabberd.
We assume that we will try to put as much library as possible into C:\sdk\
to make it easier to track what is install for ejabberd.
C:\sdk\erl5.5.5
).
C:\sdk\Expat-2.0.0
directory.Copy file C:\sdk\Expat-2.0.0\Libs\libexpat.dll
@@ -461,21 +459,20 @@ variable.
nmake -f Makefile.win32
ejabberd\src\ejabberd.cfg
and run
werl -s ejabberd -name ejabberd -
You need a Jabber account and grant him administrative privileges +
You need a Jabber account and grant him administrative privileges to enter the ejabberd Web Admin:
{acl, admins, {user, "admin1", "example.org"}}. - {access, configure, [{allow, admins}]}. +{acl, admins, {user, "admin1", "example.org"}}. +{access, configure, [{allow, admins}]}.You can grant administrative privileges to many Jabber accounts, and also to accounts in other Jabber servers.
To upgrade an ejabberd installation to a new version, +
+To upgrade an ejabberd installation to a new version, simply uninstall the old version, and then install the new one. Of course, it is important that the configuration file and Mnesia database spool directory are not removed.
ejabberd automatically updates the Mnesia table definitions at startup when needed. If you also use an external database for storage of some modules, check if the release notes of the new ejabberd version -indicates you need to also update those tables.
-The configuration file will be loaded the first time you start ejabberd. The +indicates you need to also update those tables.
+The configuration file will be loaded the first time you start ejabberd. The content from this file will be parsed and stored in the internal ejabberd database. Subsequently the configuration will be loaded from the database and any commands in the configuration file are appended to the entries in the database.
Note that ejabberd never edits the configuration file. @@ -507,43 +503,41 @@ the name of an option, and any further elements are that option’s values. configuration file do not contain for instance the ‘hosts’ option, the old host name(s) stored in the database will be used.
You can override the old values stored in the database by adding next lines to the configuration file: -
override_global. - override_local. - override_acls. +override_global. +override_local. +override_acls.With these lines the old global options (shared between all ejabberd nodes in a cluster), local options (which are specific for this particular ejabberd node) -and ACLs will be removed before new ones are added.
-3.1.1 Host Names
- +and ACLs will be removed before new ones are added.
+3.1.1 Host Names
The option hosts defines a list containing one or more domains that ejabberd will serve.
Examples:
{hosts, ["example.org"]}. +{hosts, ["example.org"]}.
{host, "example.org"}. +{host, "example.org"}.
{hosts, ["example.net", "example.com"]}. -
{hosts, ["example.net", "example.com"]}. ++
Options can be defined separately for every virtual host using the host_config option. It has the following syntax: -
{host_config, <hostname>, [<option>, <option>, ...]}. +{host_config, <hostname>, [<option>, <option>, ...]}.Examples:
{host_config, "example.net", [{auth_method, internal}]}. +{host_config, "example.net", [{auth_method, internal}]}. -{host_config, "example.com", [{auth_method, ldap}, - {ldap_servers, ["localhost"]}, - {ldap_uids, [{"uid"}]}, - {ldap_rootdn, "dc=localdomain"}, - {ldap_rootdn, "dc=example,dc=com"}, +{host_config, "example.com", [{auth_method, ldap}, + {ldap_servers, ["localhost"]}, + {ldap_uids, [{"uid"}]}, + {ldap_rootdn, "dc=localdomain"}, + {ldap_rootdn, "dc=example,dc=com"}, {ldap_password, ""}]}.
{host_config, "example.net", [{auth_method, odbc}, {odbc_server, "DSN=ejabberd;UID=ejabberd;PWD=ejabberd"}]}. -{host_config, "example.com", [{auth_method, ldap}, - {ldap_servers, ["localhost", "otherhost"]}, - {ldap_uids, [{"uid"}]}, - {ldap_rootdn, "dc=localdomain"}, - {ldap_rootdn, "dc=example,dc=com"}, +{host_config, "example.com", [{auth_method, ldap}, + {ldap_servers, ["localhost", "otherhost"]}, + {ldap_uids, [{"uid"}]}, + {ldap_rootdn, "dc=localdomain"}, + {ldap_rootdn, "dc=example,dc=com"}, {ldap_password, ""}]}.
To define specific ejabberd modules in a virtual host, you can define the global modules option with the common modules, and later add specific modules to certain virtual hosts. To accomplish that, instead of defining each option in host_config with the syntax -
{<option-name>, <option-value>} +{<option-name>, <option-value>}use this syntax: -
{{add, <option-name>}, <option-value>} +{{add, <option-name>}, <option-value>}In this example three virtual hosts have some similar modules, but there are also other different modules for some specific virtual hosts: -
% This ejabberd server has three vhosts: ++%% This ejabberd server has three vhosts: {hosts, ["one.example.org", "two.example.org", "three.example.org"]}. -% Configuration of modules that are common to all vhosts +%% Configuration of modules that are common to all vhosts {modules, [ {mod_roster, []}, @@ -581,20 +575,25 @@ other different modules for some specific virtual hosts: {mod_version, []} ]}. -% Add some modules to vhost one: -{host_config, "one.example.org", [{{add, modules}, [ - {mod_echo, [{host, "echo-service.one.example.org"}]} - {mod_http_bind, []}, - {mod_logxml, []} -]}]}. +%% Add some modules to vhost one: +{host_config, "one.example.org", + [{{add, modules}, [ + {mod_echo, [{host, "echo-service.one.example.org"}]} + {mod_http_bind, []}, + {mod_logxml, []} + ] + } + ]}. -% Add a module just to vhost two: -{host_config, "two.example.org", [{{add, modules}, [ - {mod_echo, [{host, "mirror.two.example.org"}]} -]}]}. --3.1.3 Listening Ports
- +%% Add a module just to vhost two: +{host_config, "two.example.org", + [{{add, modules}, [ + {mod_echo, [{host, "mirror.two.example.org"}]} + ] + } + ]}. +
3.1.3 Listening Ports
The option listen defines for which addresses and ports ejabberd will listen and what services will be run on them. Each element of the list is a tuple with the following elements: @@ -604,28 +603,26 @@ Port number.
The available modules, their purpose and the options allowed by each one are: -
- --
- ejabberd_c2s Description Handles c2s connections. - Options access, certfile, inet6, +
- +ejabberd_c2s
- +Handles c2s connections.
+ Options: access, certfile, inet6, ip, max_stanza_size, shaper, starttls, starttls_required, tls, -zlib- ejabberd_s2s_in Description Handles incoming s2s -connections. - Options inet6, ip, -max_stanza_size - ejabberd_service Description Interacts with -external components -(as defined in the Jabber Component Protocol (XEP-0114). - Options access, hosts, inet6, -ip, shaper, service_check_from - ejabberd_http Description Handles incoming HTTP -connections. - Options certfile, http_bind, http_poll, -inet6, ip, request_handlers, tls, web_admin
This is a detailed description of each option allowed by the listening modules: +zlib +
This is a detailed description of each option allowed by the listening modules:
{acl, blocked, {user, "bad"}}. - {access, c2s, [{deny, blocked}, - {allow, all}]}. - {shaper, normal, {maxrate, 1000}}. - {access, c2s_shaper, [{none, admin}, - {normal, all}]}. - {listen, - [{5222, ejabberd_c2s, [{access, c2s}, {shaper, c2s_shaper}]}, - {5223, ejabberd_c2s, [{access, c2s}, - ssl, {certfile, "/path/to/ssl.pem"}]}, - {5269, ejabberd_s2s_in, []}, - {5280, ejabberd_http, [http_poll, web_admin]}, - {5233, ejabberd_service, [{host, "aim.example.org", - [{password, "aimsecret"}]}]}, - {5234, ejabberd_service, [{hosts, ["icq.example.org", "sms.example.org"], - [{password, "jitsecret"}]}]}, - {5235, ejabberd_service, [{host, "msn.example.org", - [{password, "msnsecret"}]}]}, - {5236, ejabberd_service, [{host, "yahoo.example.org", - [{password, "yahoosecret"}]}]}, - {5237, ejabberd_service, [{host, "gg.example.org", - [{password, "ggsecret"}]}]}, - {5238, ejabberd_service, [{host, "jmc.example.org", - [{password, "jmcsecret"}]}]}, - {5239, ejabberd_service, [{host, "custom.example.org", - [{password, "customsecret"}]}, - {service_check_from, false}]} - ] - }. - {s2s_use_starttls, true}. - {s2s_certfile, "/path/to/ssl.pem"}. - {s2s_default_policy, deny}. - {{s2s_host,"jabber.example.org"}, allow}. - {{s2s_host,"example.com"}, allow}. ++{acl, blocked, {user, "bad"}}. +{access, c2s, [{deny, blocked}, + {allow, all}]}. +{shaper, normal, {maxrate, 1000}}. +{access, c2s_shaper, [{none, admin}, + {normal, all}]}. +{listen, + [{5222, ejabberd_c2s, [{access, c2s}, {shaper, c2s_shaper}]}, + {5223, ejabberd_c2s, [{access, c2s}, + ssl, {certfile, "/path/to/ssl.pem"}]}, + {5269, ejabberd_s2s_in, []}, + {5280, ejabberd_http, [http_poll, web_admin]}, + {5233, ejabberd_service, [{host, "aim.example.org", + [{password, "aimsecret"}]}]}, + {5234, ejabberd_service, [{hosts, ["icq.example.org", "sms.example.org"], + [{password, "jitsecret"}]}]}, + {5235, ejabberd_service, [{host, "msn.example.org", + [{password, "msnsecret"}]}]}, + {5236, ejabberd_service, [{host, "yahoo.example.org", + [{password, "yahoosecret"}]}]}, + {5237, ejabberd_service, [{host, "gg.example.org", + [{password, "ggsecret"}]}]}, + {5238, ejabberd_service, [{host, "jmc.example.org", + [{password, "jmcsecret"}]}]}, + {5239, ejabberd_service, [{host, "custom.example.org", + [{password, "customsecret"}]}, + {service_check_from, false}]} + ] +}. +{s2s_use_starttls, true}. +{s2s_certfile, "/path/to/ssl.pem"}. +{s2s_default_policy, deny}. +{{s2s_host,"jabber.example.org"}, allow}. +{{s2s_host,"example.com"}, allow}.Note, that for jabberd 1.4- or WPJabber-based services you have to make the transports log and do XDB by themselves:
<!-- @@ -866,12 +863,11 @@ services you have to make the transports log and do XDB by themselves: <spool><jabberd:cmdline flag='s'>/var/spool/jabber</jabberd:cmdline></spool> </xdb_file> </xdb> --3.1.4 Authentication
The option auth_method defines the authentication method that is used for user authentication: -
{auth_method, [<method>]}. +{auth_method, [<method>]}.The following authentication methods are supported by ejabberd:
ejabberd uses its internal Mnesia database as the default authentication method.
{auth_method, internal}. -
The anonymous authentication method can be configured with the following options. Remember that you can use the host_config option to set virtual host specific options (see section 3.1.2). Note that there also @@ -923,7 +917,7 @@ parameter (see section 3.1.2).
Examples: To enable anonymous login on all virtual hosts:
{auth_method, [anonymous]}. {anonymous_protocol, login_anon}. -
{host_config, "public.example.org", [{auth_method, [anonymous]}, {anonymous_protocol, login_anon}]}.
{host_config, "public.example.org", [{auth_method, [internal,anonymous]}, {anonymous_protocol, both}]}. -
ejabberd supports authentication via Pluggable Authentication Modules (PAM). PAM is currently supported in AIX, FreeBSD, HP-UX, Linux, Mac OS X, NetBSD and Solaris. PAM authentication is disabled by default, so you have to configure and compile @@ -953,17 +946,18 @@ PAM authentication is disabled by default, so you have to configure and compile Default is "ejabberd". Refer to the PAM documentation of your operation system for more information.
Example: -
{auth_method, [pam]}. - {pam_service, "ejabberd"}. +{auth_method, [pam]}. +{pam_service, "ejabberd"}.Though it is quite easy to set up PAM support in ejabberd, PAM itself introduces some security issues:
/var/lib/ejabberd/priv/lib/
directory. You have to set it root on execution in the case when your PAM module
requires root privileges (pam_unix.so for example). Also you have to grant access
-for ejabberd to this file and remove all other permissions from it:
-# chown root:ejabberd /var/lib/ejabberd/priv/bin/epam -# chmod 4750 /var/lib/ejabberd/priv/bin/epam +for ejabberd to this file and remove all other permissions from it. +Execute with root privileges: +chown root:ejabberd /var/lib/ejabberd/priv/bin/epam +chmod 4750 /var/lib/ejabberd/priv/bin/epam
Access control in ejabberd is performed via Access Control Lists (ACLs). The declarations of ACLs in the configuration file have the following syntax: -
{acl, <aclname>, {<acltype>, ...}}. +{acl, <aclname>, {<acltype>, ...}}.<acltype> can be one of the following:
An entry allowing or denying access to different services looks similar to this: -
{access, <accessname>, [{allow, <aclname>}, - {deny, <aclname>}, - ... - ]}. +{access, <accessname>, [{allow, <aclname>}, + {deny, <aclname>}, + ... + ]}.When a JID is checked to have access to <accessname>, the server sequentially checks if that JID matches any of the ACLs that are named in the second elements of the tuples in the list. If it matches, the first element of the first matched tuple is returned, otherwise the value ‘deny’ is returned.
Example: -
{access, configure, [{allow, admin}]}. - {access, something, [{deny, badmans}, - {allow, all}]}. +{access, configure, [{allow, admin}]}. +{access, something, [{deny, badmans}, + {allow, all}]}.The following access rules are pre-defined:
The special access max_user_sessions specifies the maximum number of sessions (authenticated connections) per user. If a user tries to open more sessions by using different resources, the first @@ -1069,36 +1059,34 @@ opened session will be disconnected. The error session replaced will be sent to the disconnected session. The value for this option can be either a number, or infinity. The default value is infinity.
The syntax is: -
{access, max_user_sessions, [{<maxnumber>, <aclname>}, - ... - ]}. +{access, max_user_sessions, [{<maxnumber>, <aclname>}, + ... + ]}.Examples:
{access, max_user_sessions, [{10, all}]}. -
{access, max_user_sessions, [{10, all}]}. ++
The special access max_s2s_connections specifies how many simultaneus S2S connections can be established to a specific remote Jabber server. The default value is 1. There’s also available the access max_s2s_connections_per_node.
The syntax is: -
{access, max_s2s_connections, [{<maxnumber>, <aclname>}, - ... - ]}. +{access, max_s2s_connections, [{<maxnumber>, <aclname>}, + ... + ]}.Examples:
{access, max_s2s_connections, [{3, all}]}. -
{access, max_s2s_connections, [{3, all}]}. ++
Shapers enable you to limit connection traffic. The syntax of shapers is like this: -
{shaper, <shapername>, <kind>}. +{shaper, <shapername>, <kind>}.Currently only one kind of shaper called maxrate is available. It has the following syntax: -
{maxrate, <rate>} +{maxrate, <rate>}where <rate> stands for the maximum allowed incoming rate in bytes per second. When a connection exceeds this limit, ejabberd stops reading from the socket @@ -1106,13 +1094,12 @@ until the average rate is again below the allowed maximum.
Examples:
{shaper, normal, {maxrate, 1000}}. +{shaper, normal, {maxrate, 1000}}.
{shaper, fast, {maxrate, 50000}}. -
{shaper, fast, {maxrate, 50000}}. ++
The option language defines the default language of server strings that can be seen by Jabber clients. If a Jabber client do not support xml:lang, the specified language is used. The default value is @@ -1120,16 +1107,15 @@ can be seen by Jabber clients. If a Jabber client do not support <language>.msg in ejabberd’s msgs directory.
Examples:
{language, "ru"}. +{language, "ru"}.
{language, "es"}. -
{language, "es"}. ++
The option include_config_file in a configuration file instructs ejabberd to include other configuration files immediately.
The basic usage is: -
{include_config_file, <filename>}. +{include_config_file, <filename>}.It is also possible to specify suboptions: -
{include_config_file, <filename>, [<suboption>, <suboption>, ...]}. +{include_config_file, <filename>, [<suboption>, <suboption>, ...]}.The filename can be indicated either as an absolute path, or relative to the main ejabberd configuration file. It isn’t possible to use wildcards. @@ -1142,26 +1128,25 @@ The default value is an empty list: [] The options that do not match this criteria are not accepted. The default value is: all
This is a basic example: -
{include_config_file, "/etc/ejabberd/additional.cfg"}. +{include_config_file, "/etc/ejabberd/additional.cfg"}.In this example, the included file is not allowed to contain a listen option. If such an option is present, the option will not be accepted. The file is in a subdirectory from where the main configuration file is. -
{include_config_file, "./example.org/additional_not_listen.cfg", [{disallow, [listen]}]}. +{include_config_file, "./example.org/additional_not_listen.cfg", [{disallow, [listen]}]}.In this example, ejabberd.cfg defines some ACL and Access rules, and later includes another file with additional rules: -
{acl, admin, {user, "admin", "localhost"}}. - {access, announce, [{allow, admin}]}. - {include_config_file, "/etc/ejabberd/acl_and_access.cfg", [{allow_only, [acl, access]}]}. +{acl, admin, {user, "admin", "localhost"}}. +{access, announce, [{allow, admin}]}. +{include_config_file, "/etc/ejabberd/acl_and_access.cfg", [{allow_only, [acl, access]}]}.and content of the file acl_and_access.cfg can be, for example: -
{acl, admin, {user, "bob", "localhost"}}. - {acl, admin, {user, "jan", "localhost"}}. --3.1.9 Option Macros in Configuration File
{acl, admin, {user, "bob", "localhost"}}. +{acl, admin, {user, "jan", "localhost"}}. ++3.1.9 Option Macros in Configuration File
In the ejabberd configuration file, it is possible to define a macro for a value and later use this macro when defining an option.
A macro is defined with this syntax: -
{define_macro, '<MACRO>', <value>}. +{define_macro, '<MACRO>', <value>}.The MACRO must be surrounded by single quotation marks, and all letters in uppercase; check the examples bellow. The value can be any valid arbitrary Erlang term.
The first definition of a macro is preserved, @@ -1179,14 +1164,14 @@ Use a macro even if it may not be defined. If the macro is not defined previously, the provided defaultvalue is used. This usage behaves as if it were defined and used this way: -
{define_macro, '<MACRO>', <defaultvalue>}. - '<MACRO>' -This example shows the basic usage of a macro: -
{define_macro, 'LOG_LEVEL_NUMBER', 5}. - {loglevel, 'LOG_LEVEL_NUMBER'}. +{define_macro, '<MACRO>', <defaultvalue>}. +'<MACRO>' +This example shows the basic usage of a macro: +
{define_macro, 'LOG_LEVEL_NUMBER', 5}. +{loglevel, 'LOG_LEVEL_NUMBER'}.The resulting option interpreted by ejabberd is: {loglevel, 5}.
This example shows that values can be any arbitrary Erlang term: -
{define_macro, 'USERBOB', {user, "bob", "localhost"}}. - {acl, admin, 'USERBOB'}. ++{define_macro, 'USERBOB', {user, "bob", "localhost"}}. +{acl, admin, 'USERBOB'}.The resulting option interpreted by ejabberd is: {acl, admin, {user, "bob", "localhost"}}.
This complex example:
{define_macro, 'NUMBER_PORT_C2S', 5222}. {define_macro, 'PORT_S2S_IN', {5269, ejabberd_s2s_in, []}}. @@ -1205,9 +1190,8 @@ This usage behaves as if it were defined and used this way: {5280, ejabberd_http, []} ] }. --3.2 Database and LDAP Configuration
3.2 Database and LDAP Configuration
ejabberd uses its internal Mnesia database by default. However, it is possible to use a relational database or an LDAP server to store persistent, @@ -1228,9 +1212,8 @@ different storage systems for modules, and so forth.
The following databas
Although this section will describe ejabberd’s configuration when you want to use the native MySQL driver, it does not describe MySQL’s installation and database creation. Check the MySQL documentation and the tutorial Using ejabberd with MySQL native driver for information regarding these topics. @@ -1245,9 +1228,8 @@ to keep alive the connections to the database. The default value is ’undefined’, so no keepalive requests are made. Specify in seconds: for example 28800 means 8 hours.
{odbc_keepalive_interval, undefined}. --
You can skip this step if you installed ejabberd using a binary installer or if the binary packages of ejabberd you are using include support for MySQL.
-The option value name may be misleading, as the auth_method name is used for access to a relational database through ODBC, as well as through the native MySQL interface. Anyway, the first configuration step is to define the odbc @@ -1279,18 +1260,16 @@ can thus take the following form:
{mysql, "Server", Port, "Database", "Username", "Password"}
The Port value should be an integer, without quotes. For example:
{odbc_server, {mysql, "localhost", Port, "test", "root", "password"}}. --
MySQL also can be used to store information into from several ejabberd modules. See section 3.3.1 to see which modules have a version with the ‘_odbc’. This suffix indicates that the module can be used with relational databases like MySQL. To enable storage to your database, just make sure that your database is running well (see previous sections), and replace the suffix-less or ldap module variant with the odbc module variant. Keep in mind -that you cannot have several variants of the same module loaded!
-- +that you cannot have several variants of the same module loaded!
+Although this section will describe ejabberd’s configuration when you want to use Microsoft SQL Server, it does not describe Microsoft SQL Server’s installation and database creation. Check the MySQL documentation and the @@ -1306,21 +1285,18 @@ to keep alive the connections to the database. The default value is ’undefined’, so no keepalive requests are made. Specify in seconds: for example 28800 means 8 hours.
{odbc_keepalive_interval, undefined}. --
You can skip this step if you installed ejabberd using a binary installer or if the binary packages of ejabberd you are using include support for ODBC.
If you want to use Microsoft SQL Server with ODBC, you need to configure, compile and install ejabberd with support for ODBC and Microsoft SQL Server enabled. This can be done, by using next commands:
./configure --enable-odbc --enable-mssql && make install --
The configuration of Microsoft SQL Server is the same as the configuration of -ODBC compatible servers (see section 3.2.4).
-- +ODBC compatible servers (see section 3.2.4).
+Microsoft SQL Server also can be used to store information into from several ejabberd modules. See section 3.3.1 to see which modules have a version with the ‘_odbc’. This suffix indicates that the module can be used @@ -1328,9 +1304,8 @@ with relational databases like Microsoft SQL Server. To enable storage to your database, just make sure that your database is running well (see previous sections), and replace the suffix-less or ldap module variant with the odbc module variant. Keep in mind that you cannot have several variants of the same -module loaded!
-Although this section will describe ejabberd’s configuration when you want to use the native PostgreSQL driver, it does not describe PostgreSQL’s installation and database creation. Check the PostgreSQL documentation and the tutorial Using ejabberd with MySQL native driver for information regarding these topics. @@ -1345,9 +1320,8 @@ to keep alive the connections to the database. The default value is ’undefined’, so no keepalive requests are made. Specify in seconds: for example 28800 means 8 hours.
{odbc_keepalive_interval, undefined}. --
You can skip this step if you installed ejabberd using a binary installer or if the binary packages of ejabberd you are using include support for PostgreSQL.
./configure --enable-odbc && make install -
The option value name may be misleading, as the auth_method name is used for access to a relational database through ODBC, as well as through the native PostgreSQL interface. Anyway, the first configuration step is to define the odbc @@ -1382,18 +1355,16 @@ can thus take the following form:
{pgsql, "Server", Port, "Database", "Username", "Password"}
The Port value should be an integer, without quotes. For example:
{odbc_server, {pgsql, "localhost", 5432, "database", "ejabberd", "password"}}. --
PostgreSQL also can be used to store information into from several ejabberd modules. See section 3.3.1 to see which modules have a version with the ‘_odbc’. This suffix indicates that the module can be used with relational databases like PostgreSQL. To enable storage to your database, just make sure that your database is running well (see previous sections), and replace the suffix-less or ldap module variant with the odbc module variant. -Keep in mind that you cannot have several variants of the same module loaded!
-- +Keep in mind that you cannot have several variants of the same module loaded!
+Although this section will describe ejabberd’s configuration when you want to use the ODBC driver, it does not describe the installation and database creation of your database. Check the documentation of your database. The tutorial Using ejabberd with MySQL native driver also can help you. Note that the tutorial @@ -1406,9 +1377,8 @@ to keep alive the connections to the database. The default value is ’undefined’, so no keepalive requests are made. Specify in seconds: for example 28800 means 8 hours.
{odbc_keepalive_interval, undefined}. --
You can skip this step if you installed ejabberd using a binary installer or +
+You can skip this step if you installed ejabberd using a binary installer or if the binary packages of ejabberd you are using include support for ODBC.
./configure --enable-odbc && make install -
The first configuration step is to define the odbc auth_method. For example:
{host_config, "public.example.org", [{auth_method, [odbc]}]}. @@ -1428,9 +1397,8 @@ value is used to defined if we want to use ODBC, or one of the two native interface available, PostgreSQL or MySQL.+To use a relational database through ODBC, you can pass the ODBC connection string as odbc_server parameter. For example:
{odbc_server, "DSN=database;UID=ejabberd;PWD=password"}. --Storage
An ODBC compatible database also can be used to store information into from several ejabberd modules. See section 3.3.1 to see which modules have a version with the ‘_odbc’. This suffix indicates that the module @@ -1438,14 +1406,12 @@ can be used with ODBC compatible relational databases. To enable storage to your database, just make sure that your database is running well (see previous sections), and replace the suffix-less or ldap module variant with the odbc module variant. Keep in mind that you cannot have several variants of the same -module loaded!
-ejabberd has built-in LDAP support. You can authenticate users against LDAP server and use LDAP directory as vCard storage. Shared rosters are not supported -yet.
-Parameters: +yet.
+Parameters:
Example: -
{auth_method, ldap}. - {ldap_servers, ["ldap.example.org"]}. - {ldap_port, 389}. - {ldap_rootdn, "cn=Manager,dc=domain,dc=org"}. - {ldap_password, "secret"}. +{auth_method, ldap}. +{ldap_servers, ["ldap.example.org"]}. +{ldap_port, 389}. +{ldap_rootdn, "cn=Manager,dc=domain,dc=org"}. +{ldap_password, "secret"}.Note that current LDAP implementation does not support SSL secured communication -and SASL authentication.
-Authentication
You can authenticate users against an LDAP directory. Available options are:
You can authenticate users against an LDAP directory. Available options are:
Let’s say ldap.example.org is the name of our LDAP server. We have +
Let’s say ldap.example.org is the name of our LDAP server. We have users with their passwords in "ou=Users,dc=example,dc=org" directory. Also we have addressbook, which contains users emails and their additional infos in "ou=AddressBook,dc=example,dc=org" directory. Corresponding -authentication section should looks like this:
%% authentication method - {auth_method, ldap}. - %% DNS name of our LDAP server - {ldap_servers, ["ldap.example.org"]}. - %% Bind to LDAP server as "cn=Manager,dc=example,dc=org" with password "secret" - {ldap_rootdn, "cn=Manager,dc=example,dc=org"}. - {ldap_password, "secret"}. - %% define the user's base - {ldap_base, "ou=Users,dc=example,dc=org"}. - %% We want to authorize users from 'shadowAccount' object class only - {ldap_filter, "(objectClass=shadowAccount)"}. +authentication section should looks like this:%% Authentication method +{auth_method, ldap}. +%% DNS name of our LDAP server +{ldap_servers, ["ldap.example.org"]}. +%% Bind to LDAP server as "cn=Manager,dc=example,dc=org" with password "secret" +{ldap_rootdn, "cn=Manager,dc=example,dc=org"}. +{ldap_password, "secret"}. +%% Define the user's base +{ldap_base, "ou=Users,dc=example,dc=org"}. +%% We want to authorize users from 'shadowAccount' object class only +{ldap_filter, "(objectClass=shadowAccount)"}.Now we want to use users LDAP-info as their vCards. We have four attributes defined in our LDAP schema: "mail" — email address, "givenName" — first name, "sn" — second name, "birthDay" — birthday. -Also we want users to search each other. Let’s see how we can set it up:
{modules, - ... - {mod_vcard_ldap, - [ - %% We use the same server and port, but want to bind anonymously because - %% our LDAP server accepts anonymous requests to - %% "ou=AddressBook,dc=example,dc=org" subtree. - {ldap_rootdn, ""}, - {ldap_password, ""}, - %% define the addressbook's base - {ldap_base, "ou=AddressBook,dc=example,dc=org"}, - %% uidattr: user's part of JID is located in the "mail" attribute - %% uidattr_format: common format for our emails - {ldap_uids, [{"mail", "%u@mail.example.org"}]}, - %% We have to define empty filter here, because entries in addressbook does not - %% belong to shadowAccount object class - {ldap_filter, ""}, - %% Now we want to define vCard pattern - {ldap_vcard_map, - [{"NICKNAME", "%u", []}, % just use user's part of JID as his nickname - {"GIVEN", "%s", ["givenName"]}, - {"FAMILY", "%s", ["sn"]}, - {"FN", "%s, %s", ["sn", "givenName"]}, % example: "Smith, John" - {"EMAIL", "%s", ["mail"]}, - {"BDAY", "%s", ["birthDay"]}]}, - %% Search form - {ldap_search_fields, - [{"User", "%u"}, - {"Name", "givenName"}, - {"Family Name", "sn"}, - {"Email", "mail"}, - {"Birthday", "birthDay"}]}, - %% vCard fields to be reported - %% Note that JID is always returned with search results - {ldap_search_reported, - [{"Full Name", "FN"}, - {"Nickname", "NICKNAME"}, - {"Birthday", "BDAY"}]} - ]}, - ... - }. +Also we want users to search each other. Let’s see how we can set it up:{modules, + [ + ... + {mod_vcard_ldap, + [ + %% We use the same server and port, but want to bind anonymously because + %% our LDAP server accepts anonymous requests to + %% "ou=AddressBook,dc=example,dc=org" subtree. + {ldap_rootdn, ""}, + {ldap_password, ""}, + %% define the addressbook's base + {ldap_base, "ou=AddressBook,dc=example,dc=org"}, + %% uidattr: user's part of JID is located in the "mail" attribute + %% uidattr_format: common format for our emails + {ldap_uids, [{"mail", "%u@mail.example.org"}]}, + %% We have to define empty filter here, because entries in addressbook does not + %% belong to shadowAccount object class + {ldap_filter, ""}, + %% Now we want to define vCard pattern + {ldap_vcard_map, + [{"NICKNAME", "%u", []}, % just use user's part of JID as his nickname + {"GIVEN", "%s", ["givenName"]}, + {"FAMILY", "%s", ["sn"]}, + {"FN", "%s, %s", ["sn", "givenName"]}, % example: "Smith, John" + {"EMAIL", "%s", ["mail"]}, + {"BDAY", "%s", ["birthDay"]}]}, + %% Search form + {ldap_search_fields, + [{"User", "%u"}, + {"Name", "givenName"}, + {"Family Name", "sn"}, + {"Email", "mail"}, + {"Birthday", "birthDay"}]}, + %% vCard fields to be reported + %% Note that JID is always returned with search results + {ldap_search_reported, + [{"Full Name", "FN"}, + {"Nickname", "NICKNAME"}, + {"Birthday", "BDAY"}]} + ]}, + ... + ]}.Note that mod_vcard_ldap module checks for the existence of the user before -searching in his information in LDAP.
-Active Directory
- +searching in his information in LDAP.
+Active Directory
Active Directory is just an LDAP-server with predefined attributes. A sample -configuration is shown below:
{auth_method, ldap}. - {ldap_servers, ["office.org"]}. % List of LDAP servers - {ldap_base, "DC=office,DC=org"}. % Search base of LDAP directory - {ldap_rootdn, "CN=Administrator,CN=Users,DC=office,DC=org"}. % LDAP manager - {ldap_password, "*******"}. % Password to LDAP manager - {ldap_uids, [{"sAMAccountName"}]}. - {ldap_filter, "(memberOf=*)"}. +configuration is shown below:+{auth_method, ldap}. +{ldap_servers, ["office.org"]}. % List of LDAP servers +{ldap_base, "DC=office,DC=org"}. % Search base of LDAP directory +{ldap_rootdn, "CN=Administrator,CN=Users,DC=office,DC=org"}. % LDAP manager +{ldap_password, "*******"}. % Password to LDAP manager +{ldap_uids, [{"sAMAccountName"}]}. +{ldap_filter, "(memberOf=*)"}. - {modules, - ... - {mod_vcard_ldap, - [{ldap_vcard_map, - [{"NICKNAME", "%u", []}, - {"GIVEN", "%s", ["givenName"]}, - {"MIDDLE", "%s", ["initials"]}, - {"FAMILY", "%s", ["sn"]}, - {"FN", "%s", ["displayName"]}, - {"EMAIL", "%s", ["mail"]}, - {"ORGNAME", "%s", ["company"]}, - {"ORGUNIT", "%s", ["department"]}, - {"CTRY", "%s", ["c"]}, - {"LOCALITY", "%s", ["l"]}, - {"STREET", "%s", ["streetAddress"]}, - {"REGION", "%s", ["st"]}, - {"PCODE", "%s", ["postalCode"]}, - {"TITLE", "%s", ["title"]}, - {"URL", "%s", ["wWWHomePage"]}, - {"DESC", "%s", ["description"]}, - {"TEL", "%s", ["telephoneNumber"]}]}, - {ldap_search_fields, - [{"User", "%u"}, - {"Name", "givenName"}, - {"Family Name", "sn"}, - {"Email", "mail"}, - {"Company", "company"}, - {"Department", "department"}, - {"Role", "title"}, - {"Description", "description"}, - {"Phone", "telephoneNumber"}]}, - {ldap_search_reported, - [{"Full Name", "FN"}, - {"Nickname", "NICKNAME"}, - {"Email", "EMAIL"}]} - ]}, - ... - }. --3.3 Modules Configuration
- +{modules, + [ + ... + {mod_vcard_ldap, + [{ldap_vcard_map, + [{"NICKNAME", "%u", []}, + {"GIVEN", "%s", ["givenName"]}, + {"MIDDLE", "%s", ["initials"]}, + {"FAMILY", "%s", ["sn"]}, + {"FN", "%s", ["displayName"]}, + {"EMAIL", "%s", ["mail"]}, + {"ORGNAME", "%s", ["company"]}, + {"ORGUNIT", "%s", ["department"]}, + {"CTRY", "%s", ["c"]}, + {"LOCALITY", "%s", ["l"]}, + {"STREET", "%s", ["streetAddress"]}, + {"REGION", "%s", ["st"]}, + {"PCODE", "%s", ["postalCode"]}, + {"TITLE", "%s", ["title"]}, + {"URL", "%s", ["wWWHomePage"]}, + {"DESC", "%s", ["description"]}, + {"TEL", "%s", ["telephoneNumber"]}]}, + {ldap_search_fields, + [{"User", "%u"}, + {"Name", "givenName"}, + {"Family Name", "sn"}, + {"Email", "mail"}, + {"Company", "company"}, + {"Department", "department"}, + {"Role", "title"}, + {"Description", "description"}, + {"Phone", "telephoneNumber"}]}, + {ldap_search_reported, + [{"Full Name", "FN"}, + {"Nickname", "NICKNAME"}, + {"Email", "EMAIL"}]} + ]}, + ... + ]}. +
3.3 Modules Configuration
The option modules defines the list of modules that will be loaded after ejabberd’s startup. Each entry in the list is a tuple in which the first element is the name of a module and the second is a list of options for that @@ -1618,58 +1582,57 @@ module.
Examples:
{modules, - [{mod_echo, []} - ]}. +{modules, + [ + {mod_echo, []} + ]}.
{modules, - [{mod_echo, []}, - {mod_time, []}, - {mod_version, []} - ]}. -
{modules, + [ + {mod_echo, []}, + {mod_time, []}, + {mod_version, []} + ]}. ++
The following table lists all modules included in ejabberd.
- --
- Module Feature Dependencies Needed for XMPP? - mod_adhoc Ad-Hoc Commands (XEP-0050) No - mod_announce Manage announcements recommends mod_adhoc No - mod_caps Request and cache Entity Capabilities (XEP-0115) No - mod_configure Server configuration using Ad-Hoc mod_adhoc No - mod_disco Service Discovery (XEP-0030) No - mod_echo Echoes Jabber packets No - mod_irc IRC transport No - mod_last Last Activity (XEP-0012) No - mod_last_odbc Last Activity (XEP-0012) supported database (*) No - mod_muc Multi-User Chat (XEP-0045) No - mod_muc_log Multi-User Chat room logging mod_muc No - mod_offline Offline message storage No - mod_offline_odbc Offline message storage supported database (*) No - mod_privacy Blocking Communications Yes - mod_privacy_odbc Blocking Communications supported database (*) Yes - mod_private Private XML Storage (XEP-0049) No - mod_private_odbc Private XML Storage (XEP-0049) supported database (*) No - mod_proxy65 SOCKS5 Bytestreams (XEP-0065) No - mod_pubsub Publish-Subscribe (XEP-0060) and PEP (XEP-0163) mod_caps No - mod_register In-Band Registration (XEP-0077) No - mod_roster Roster management Yes (**) - mod_roster_odbc Roster management supported database (*) Yes (**) - mod_service_log Copy user messages to logger service No - mod_shared_roster Shared roster management mod_roster or No - mod_roster_odbc - mod_stats Statistics Gathering (XEP-0039) No - mod_time Entity Time (XEP-0090) No - mod_vcard vcard-temp (XEP-0054) No - mod_vcard_ldap vcard-temp (XEP-0054) LDAP server No - mod_vcard_odbc vcard-temp (XEP-0054) supported database (*) No + mod_version Software Version (XEP-0092) No
+ Module Feature Dependencies + mod_adhoc Ad-Hoc Commands (XEP-0050) + mod_announce Manage announcements recommends mod_adhoc + mod_caps Entity Capabilities (XEP-0115) + mod_configure Server configuration using Ad-Hoc mod_adhoc + mod_disco Service Discovery (XEP-0030) + mod_echo Echoes Jabber packets + mod_irc IRC transport + mod_last Last Activity (XEP-0012) + mod_last_odbc Last Activity (XEP-0012) supported DB (*) + mod_muc Multi-User Chat (XEP-0045) + mod_muc_log Multi-User Chat room logging mod_muc + mod_offline Offline message storage (XEP-0160) + mod_offline_odbc Offline message storage (XEP-0160) supported DB (*) + mod_privacy Blocking Communication (XMPP IM) + mod_privacy_odbc Blocking Communication (XMPP IM) supported DB (*) + mod_private Private XML Storage (XEP-0049) + mod_private_odbc Private XML Storage (XEP-0049) supported DB (*) + mod_proxy65 SOCKS5 Bytestreams (XEP-0065) + mod_pubsub Pub-Sub (XEP-0060), PEP (XEP-0163) mod_caps + mod_register In-Band Registration (XEP-0077) + mod_roster Roster management (XMPP IM) + mod_roster_odbc Roster management (XMPP IM) supported DB (*) + mod_service_log Copy user messages to logger service + mod_shared_roster Shared roster management mod_roster or + mod_roster_odbc + mod_stats Statistics Gathering (XEP-0039) + mod_time Entity Time (XEP-0090) + mod_vcard vcard-temp (XEP-0054) + mod_vcard_ldap vcard-temp (XEP-0054) LDAP server + mod_vcard_odbc vcard-temp (XEP-0054) supported DB (*) mod_version Software Version (XEP-0092)
- -(*) For a list of supported databases, see section 3.2. -
- (**) This module or a similar one with another database backend is needed for -XMPP compliancy. +(*) This module requires a supported database. For a list of supported databases, see section 3.2.
You can see which database backend each module needs by looking at the suffix:
+
- No suffix, this means that the modules uses Erlang’s built-in database @@ -1694,12 +1657,10 @@ Last connection date and time: Use mod_last_odbc instead of contributed modules on the ejabberd website. Please remember that these contributions might not work or that they can contain severe bugs and security leaks. Therefore, use them at -your own risk! -
3.3.2 Common Options
The following options are used by many modules. Therefore, they are described in -this separate section.
-iqdisc
+3.3.2 Common Options
The following options are used by many modules. Therefore, they are described in +this separate section.
+iqdisc
Many modules define handlers for processing IQ queries of different namespaces to this server or to a user (e. g. to example.org or to user@example.org). This option defines processing discipline for @@ -1713,7 +1674,7 @@ recommended if the processing of a query can take a relatively long time. of IQ queries of a namespace with this discipline. In addition, the processing of this queue is done in parallel with that of other packets. This discipline is most recommended. -
- {queues, N}
- : N separate queues are created to process the +
- {queues, N}
- N separate queues are created to process the queries. The queries are thus process in parallel, but in a controlled way.
- parallel
- For every packet with this discipline a separate Erlang process @@ -1722,36 +1683,34 @@ Although spawning of Erlang process has a relatively low cost, this can break the server’s normal work, because the Erlang emulator has a limit on the number of processes (32000 by default).
Example: -
{modules, - [ - ... - {mod_time, [{iqdisc, no_queue}]}, - ... - ]}. --host
{modules, + [ + ... + {mod_time, [{iqdisc, no_queue}]}, + ... + ]}. ++host
This option defines the Jabber ID of a service provided by an ejabberd module. The keyword "@HOST@" is replaced at start time with the real virtual host string.
This example configures the echo module to provide its echoing service in the Jabber ID mirror.example.org: -
{modules, - [ - ... - {mod_echo, [{host, "mirror.example.org"}]}, - ... - ]}. +{modules, + [ + ... + {mod_echo, [{host, "mirror.example.org"}]}, + ... + ]}.However, if there are several virtual hosts and this module is enabled in all of them, the "@HOST@" keyword must be used: -
{modules, - [ - ... - {mod_echo, [{host, "mirror.@HOST@"}]}, - ... - ]}. --3.3.3 mod_announce
{modules, + [ + ... + {mod_echo, [{host, "mirror.@HOST@"}]}, + ... + ]}. ++3.3.3 mod_announce
This module enables configured users to broadcast announcements and to set the message of the day (MOTD). Configured users can perform these actions with a @@ -1788,35 +1747,37 @@ able to send such messages).
Examples:
- Only administrators can send announcements: -
{access, announce, [{allow, admins}]}. +{access, announce, [{allow, admins}]}. - {modules, - [ - ... - {mod_adhoc, []}, - {mod_announce, [{access, announce}]}, - ... - ]}. +{modules, + [ + ... + {mod_adhoc, []}, + {mod_announce, [{access, announce}]}, + ... + ]}.- Administrators as well as the direction can send announcements: -
{acl, direction, {user, "big_boss", "example.org"}}. - {acl, direction, {user, "assistant", "example.org"}}. - {acl, admins, {user, "admin", "example.org"}}. +{acl, direction, {user, "big_boss", "example.org"}}. +{acl, direction, {user, "assistant", "example.org"}}. +{acl, admins, {user, "admin", "example.org"}}. + +{access, announce, [{allow, admins}, + {allow, direction}]}. + +{modules, + [ ... - {access, announce, [{allow, admins}, - {allow, direction}]}. + {mod_adhoc, []}, + {mod_announce, [{access, announce}]}, ... - {modules, - [ - ... - {mod_adhoc, []}, - {mod_announce, [{access, announce}]}, - ... - ]}. + ]}.Note that mod_announce can be resource intensive on large deployments as it can broadcast lot of messages. This module should be -disabled for instances of ejabberd with hundreds of thousands users.
-3.3.4 mod_disco
- +disabled for instances of ejabberd with hundreds of thousands users.
+3.3.4 mod_disco
This module adds support for Service Discovery (XEP-0030). With this module enabled, services on your server can be discovered by Jabber clients. Note that ejabberd has no modules with support @@ -1833,31 +1794,30 @@ extra domains can be added to the Service Discovery item list.
Examples:
-
- To serve a link to the Jabber User Directory on jabber.org: -
{modules, - [ - ... - {mod_disco, [{extra_domains, ["users.jabber.org"]}]}, - ... - ]}. +{modules, + [ + ... + {mod_disco, [{extra_domains, ["users.jabber.org"]}]}, + ... + ]}.- To serve a link to the transports on another server: -
{modules, - [ - ... - {mod_disco, [{extra_domains, ["icq.example.com", - "msn.example.com"]}]}, - ... - ]}. +{modules, + [ + ... + {mod_disco, [{extra_domains, ["icq.example.com", + "msn.example.com"]}]}, + ... + ]}.- To serve a link to a few friendly servers: -
{modules, - [ - ... - {mod_disco, [{extra_domains, ["example.org", - "example.com"]}]}, - ... - ]}. -3.3.5 mod_echo
{modules, + [ + ... + {mod_disco, [{extra_domains, ["example.org", + "example.com"]}]}, + ... + ]}. +3.3.5 mod_echo
This module simply echoes any Jabber packet back to the sender. This mirror can be of interest for ejabberd and Jabber client debugging.
Options: @@ -1870,15 +1830,14 @@ is replaced at start time with the real virtual host name.
Example: Mirror, mirror, on the wall, who is the most beautiful of them all? -
{modules, - [ - ... - {mod_echo, [{host, "mirror.example.org"}]}, - ... - ]}. --3.3.6 mod_irc
{modules, + [ + ... + {mod_echo, [{host, "mirror.example.org"}]}, + ... + ]}. ++3.3.6 mod_irc
This module is an IRC transport that can be used to join channels on IRC servers.
End user information: @@ -1913,32 +1872,31 @@ may use the IRC transport (default value: all). In the first example, the IRC transport is available on (all) your virtual host(s) with the prefix ‘irc.’. Furthermore, anyone is able to use the transport. The default encoding is set to "iso8859-15". -
{modules, - [ - ... - {mod_irc, [{access, all}, {default_encoding, "iso8859-15"}]}, - ... - ]}. +{modules, + [ + ... + {mod_irc, [{access, all}, {default_encoding, "iso8859-15"}]}, + ... + ]}.In next example the IRC transport is available with JIDs with prefix irc-t.net. Moreover, the transport is only accessible by paying customers registered on our domains and on other servers. - -{acl, paying_customers, {user, "customer1", "example.net"}}. - {acl, paying_customers, {user, "customer2", "example.com"}}. - {acl, paying_customers, {user, "customer3", "example.org"}}. - ... - {access, paying_customers, [{allow, paying_customers}, +{acl, paying_customers, {user, "customer1", "example.net"}}. +{acl, paying_customers, {user, "customer2", "example.com"}}. +{acl, paying_customers, {user, "customer3", "example.org"}}. + +{access, paying_customers, [{allow, paying_customers}, {deny, all}]}. + +{modules, + [ ... - {modules, - [ - ... - {mod_irc, [{access, paying_customers}, - {host, "irc.example.net"}]}, - ... - ]}. -3.3.7 mod_last
- + {mod_irc, [{access, paying_customers}, + {host, "irc.example.net"}]}, + ... + ]}. +
+3.3.7 mod_last
This module adds support for Last Activity (XEP-0012). It can be used to discover when a disconnected user last accessed the server, to know when a connected user was last active on the server, or to query the uptime of the @@ -1946,9 +1904,8 @@ connected user was last active on the server, or to query the uptime of the
-
- iqdisc
- This specifies the processing discipline for Last activity (jabber:iq:last) IQ queries (see section 3.3.2). -
3.3.8 mod_muc
+3.3.8 mod_muc
With this module enabled, your server will support Multi-User Chat (XEP-0045). End users will be able to join text conferences.
Some of the features of Multi-User Chat:
-
- @@ -2051,7 +2008,7 @@ The available room options and the default values are:
- {logging, false}
- The public messages are logged using mod_muc_log.
- {max_users, 200}
- Maximum number of occupants in the room.
- {members_by_default, true}
- The occupants that enter the room are participants by default, so they have ’voice’. -
- {members_only, false}
- Only members of the room can enter. +
- {members_only, false}
- Only members of the room can enter.
- {moderated, true}
- Only occupants with ’voice’ can send public messages.
- {password, ""}
- Password of the room. You may want to enable the next option too.
- {password_protected, false}
- The password is required to enter the room. @@ -2074,19 +2031,19 @@ to new hardware. This will involve service breakdowns around 23:00 UMT. We apologise for this inconvenience.’ to conference.example.org, it will be displayed in all active rooms. In this example the history feature is disabled. -
{acl, admins, {user, "admin", "example.org"}}. +{acl, admins, {user, "admin", "example.org"}}. + +{access, muc_admins, [{allow, admins}]}. + +{modules, + [ ... - {access, muc_admins, [{allow, admins}]}. + {mod_muc, [{access, all}, + {access_create, all}, + {access_admin, muc_admins}, + {history_size, 0}]}, ... - {modules, - [ - ... - {mod_muc, [{access, all}, - {access_create, all}, - {access_admin, muc_admins}, - {history_size, 0}]}, - ... - ]}. + ]}.- In the second example the Multi-User Chat service is only accessible by paying customers registered on our domains and on other servers. Of course the administrator is also allowed to access rooms. In addition, he is the @@ -2097,57 +2054,56 @@ around 23:00 UMT. We apologise for this inconvenience.’ to conference.example.org, it will be displayed in all active rooms. No history_size option is used, this means that the feature is enabled and the default value of 20 history messages will be send to the users. -
{acl, paying_customers, {user, "customer1", "example.net"}}. - {acl, paying_customers, {user, "customer2", "example.com"}}. - {acl, paying_customers, {user, "customer3", "example.org"}}. - {acl, admins, {user, "admin", "example.org"}}. +{acl, paying_customers, {user, "customer1", "example.net"}}. +{acl, paying_customers, {user, "customer2", "example.com"}}. +{acl, paying_customers, {user, "customer3", "example.org"}}. +{acl, admins, {user, "admin", "example.org"}}. + +{access, muc_admins, [{allow, admins}, + {deny, all}]}. +{access, muc_access, [{allow, paying_customers}, + {allow, admins}, + {deny, all}]}. + +{modules, + [ ... - {access, muc_admins, [{allow, admins}, - {deny, all}]}. - {access, muc_access, [{allow, paying_customers}, - {allow, admins}, - {deny, all}]}. + {mod_muc, [{access, muc_access}, + {access_create, muc_admins}, + {access_admin, muc_admins}]}, ... - {modules, - [ - ... - {mod_muc, [{access, muc_access}, - {access_create, muc_admins}, - {access_admin, muc_admins}]}, - ... - ]}. + ]}.- In the following example, MUC anti abuse options are used. A user cannot send more than one message every 0.4 seconds and cannot change its presence more than once every 4 seconds. No ACLs are -defined, but some user restriction could be added as well:
... - {modules, - [ - ... - {mod_muc, [{min_message_interval, 0.4}, - {min_presence_interval, 4}]}, - ... - ]}. +defined, but some user restriction could be added as well:{modules, + [ + ... + {mod_muc, [{min_message_interval, 0.4}, + {min_presence_interval, 4}]}, + ... + ]}.- This example shows how to use default_room_options to make sure newly created chatrooms have by default those options. -
{modules, - [ - ... - {mod_muc, [{access, muc_access}, - {access_create, muc_admins}, - {default_room_options, [ - {allow_change_subj, false}, - {allow_query_users, true}, - {allow_private_messages, true}, - {members_by_default, false}, - {title, "New chatroom"}, - {anonymous, false} - ]}, - {access_admin, muc_admins}]}, - ... - ]}. -3.3.9 mod_muc_log
{modules, + [ + ... + {mod_muc, [{access, muc_access}, + {access_create, muc_admins}, + {default_room_options, + [ + {allow_change_subj, false}, + {allow_query_users, true}, + {allow_private_messages, true}, + {members_by_default, false}, + {title, "New chatroom"}, + {anonymous, false} + ]}, + {access_admin, muc_admins}]}, + ... + ]}. ++3.3.9 mod_muc_log
This module enables optional logging of Multi-User Chat (MUC) conversations to HTML. Once you enable this module, users can join a chatroom using a MUC capable Jabber client, and if they have enough privileges, they can request the @@ -2213,49 +2169,48 @@ of the log files will contain the full date, and there will be no subdirectories. The log files will be stored in /var/www/muclogs, and the time zone will be GMT/UTC. Finally, the top link will be
<a href="http://www.jabber.ru">Jabber.ru</a>
. -{access, muc, [{allow, all}]}. +{access, muc, [{allow, all}]}. + +{modules, + [ ... - {modules, - [ - ... - {mod_muc_log, [ - {access_log, muc}, - {cssfile, "http://example.com/my.css"}, - {dirtype, plain}, - {outdir, "/var/www/muclogs"}, - {timezone, universal}, - {spam_prevention, true}, - {top_link, {"http://www.jabber.ru", "Jabber.ru"}} - ]}, - ... - ]}. + {mod_muc_log, [ + {access_log, muc}, + {cssfile, "http://example.com/my.css"}, + {dirtype, plain}, + {outdir, "/var/www/muclogs"}, + {timezone, universal}, + {spam_prevention, true}, + {top_link, {"http://www.jabber.ru", "Jabber.ru"}} + ]}, + ... + ]}.In the second example only admin1@example.org and admin2@example.net can enable logging, and the embedded CSS file will be used. Further, the names of the log files will only contain the day (number), and there will be subdirectories for each year and month. The log files will be stored in /var/www/muclogs, and the local time will be used. Finally, the top link will be the default -<a href="/">Home</a>
. -{acl, admins, {user, "admin1", "example.org"}}. - {acl, admins, {user, "admin2", "example.net"}}. +{acl, admins, {user, "admin1", "example.org"}}. +{acl, admins, {user, "admin2", "example.net"}}. + +{access, muc_log, [{allow, admins}, + {deny, all}]}. + +{modules, + [ ... - {access, muc_log, [{allow, admins}, - {deny, all}]}. + {mod_muc_log, [ + {access_log, muc_log}, + {cssfile, false}, + {dirtype, subdirs}, + {outdir, "/var/www/muclogs"}, + {timezone, local} + ]}, ... - {modules, - [ - ... - {mod_muc_log, [ - {access_log, muc_log}, - {cssfile, false}, - {dirtype, subdirs}, - {outdir, "/var/www/muclogs"}, - {timezone, local} - ]}, - ... - ]}. -3.3.10 mod_offline
+3.3.10 mod_offline
This module implements offline message storage. This means that all messages sent to an offline user will be stored on the server until that user comes online again. Thus it is very similar to how email works. Note that @@ -2265,9 +2220,8 @@ online again. Thus it is very similar to how email works. Note that is use to set a max number of offline messages per user (quota). Its value can be either infinity or a strictly positive integer. The default value is infinity. - -
3.3.11 mod_privacy
+3.3.11 mod_privacy
This module implements Blocking Communication (also known as Privacy Rules) as defined in section 10 from XMPP IM. If end users have support for it in their Jabber client, they will be able to: @@ -2294,9 +2248,8 @@ subscription type (or globally).
-
- iqdisc
- This specifies the processing discipline for Blocking Communication (jabber:iq:privacy) IQ queries (see section 3.3.2). -
3.3.12 mod_private
+3.3.12 mod_private
This module adds support for Private XML Storage (XEP-0049):
Using this method, Jabber entities can store private data on the server and @@ -2307,9 +2260,8 @@ of client-specific preferences; another is Bookmark Storage (iqdisc This specifies the processing discipline for Private XML Storage (jabber:iq:private) IQ queries (see section 3.3.2). - -3.3.13 mod_proxy65
+3.3.13 mod_proxy65
This module implements SOCKS5 Bytestreams (XEP-0065). It allows ejabberd to act as a file transfer proxy between two XMPP clients.
Options: @@ -2337,35 +2289,34 @@ Default is none.
Examples:
-
- The simpliest configuration of the module: -
{modules, - [ - ... - {mod_proxy65, []}, - ... - ]}. +{modules, + [ + ... + {mod_proxy65, []}, + ... + ]}.- More complicated configuration. -
{acl, proxy_users, {server, "example.org"}}. - {access, proxy65_access, [{allow, proxy_users}, {deny, all}]}. +{acl, proxy_users, {server, "example.org"}}. +{access, proxy65_access, [{allow, proxy_users}, {deny, all}]}. + +{acl, admin, {user, "admin", "example.org"}}. +{shaper, normal, {maxrate, 10240}}. %% 10 Kbytes/sec +{access, proxy65_shaper, [{none, admin}, {normal, all}]}. + +{modules, + [ ... - {acl, admin, {user, "admin", "example.org"}}. - {shaper, normal, {maxrate, 10240}}. %% 10 Kbytes/sec - {access, proxy65_shaper, [{none, admin}, {normal, all}]}. + {mod_proxy65, [{host, "proxy1.example.org"}, + {name, "File Transfer Proxy"}, + {ip, {200,150,100,1}}, + {port, 7778}, + {max_connections, 5}, + {access, proxy65_access}, + {shaper, proxy65_shaper}]}, ... - {modules, - [ - ... - {mod_proxy65, [{host, "proxy1.example.org"}, - {name, "File Transfer Proxy"}, - {ip, {200,150,100,1}}, - {port, 7778}, - {max_connections, 5}, - {access, proxy65_access}, - {shaper, proxy65_shaper}]}, - ... - ]}. -3.3.14 mod_pubsub
+3.3.14 mod_pubsub
This module offers a Publish-Subscribe Service (XEP-0060). The functionality in mod_pubsub can be extended using plugins. The plugin that implements PEP (Personal Eventing via Pubsub) (XEP-0163) @@ -2386,18 +2337,17 @@ pubsub plugin is always used. nodetree is used. Nodetrees are default and virtual. Only one nodetree can be used and is shared by all node plugins.
Example: -
{modules, - [ - ... - {mod_pubsub, [ - {access_createnode, pubsub_createnode}, - {plugins, ["default", "pep"]} - ]} - ... - ]}. --3.3.15 mod_register
{modules, + [ + ... + {mod_pubsub, [ + {access_createnode, pubsub_createnode}, + {plugins, ["default", "pep"]} + ]} + ... + ]}. ++3.3.15 mod_register
This module adds support for In-Band Registration (XEP-0077). This protocol enables end users to use a Jabber client to:
+
- @@ -2428,55 +2378,54 @@ instead of an integer put a word like: infinity. Default value: 600 seconds.
Examples:
-
- Next example prohibits the registration of too short account names: -
{acl, shortname, {user_glob, "?"}}. - {acl, shortname, {user_glob, "??"}}. - % The same using regexp: - %{acl, shortname, {user_regexp, "^..?$"}}. +{acl, shortname, {user_glob, "?"}}. +{acl, shortname, {user_glob, "??"}}. +%% The same using regexp: +%%{acl, shortname, {user_regexp, "^..?$"}}. + +{access, register, [{deny, shortname}, + {allow, all}]}. + +{modules, + [ ... - {access, register, [{deny, shortname}, - {allow, all}]}. + {mod_register, [{access, register}]}, ... - {modules, - [ - ... - {mod_register, [{access, register}]}, - ... - ]}. + ]}.- The in-band registration of new accounts can be prohibited by changing the access option. If you really want to disable all In-Band Registration functionality, that is changing passwords in-band and deleting accounts in-band, you have to remove mod_register from the modules list. In this example all In-Band Registration functionality is disabled: -
{access, register, [{deny, all}]}. +{access, register, [{deny, all}]}. - {modules, - [ - ... -% {mod_register, [{access, register}]}, - ... - ]}. -- Define the welcome message and three registration watchers. +{modules, + [ + ... + %% {mod_register, [{access, register}]}, + ... + ]}. +
- Define the welcome message and two registration watchers. Also define a registration timeout of one hour: -
{registration_timeout, 3600}. - {modules, +{registration_timeout, 3600}. +{modules, + [ + ... + {mod_register, [ - ... - {mod_register, [ - {welcome_message, {"Welcome!", "Welcome to this Jabber server. For information about Jabber visit http://www.jabber.org"}}, - {registration_watchers, ["admin1@example.org", "admin2@example.org", "boss@example.net"]} - ]}, - ... - ]}. -3.3.16 mod_roster
- + {welcome_message, {"Welcome!", "Welcome to this Jabber server. Check http://www.jabber.org"}}, + {registration_watchers, ["admin1@example.org", "boss@example.net"]} + ]}, + ... + ]}. +
3.3.16 mod_roster
This module implements roster management as defined in RFC 3921: XMPP IM.
Options:
-
- iqdisc
- This specifies the processing discipline for Roster Management (jabber:iq:roster) IQ queries (see section 3.3.2). -
3.3.17 mod_service_log
+3.3.17 mod_service_log
This module adds support for logging end user packets via a Jabber message auditing service such as Bandersnatch. All user @@ -2489,25 +2438,24 @@ that will receive the packets can be specified.
-
- To log all end user packets to the Bandersnatch service running on bandersnatch.example.com: -
{modules, - [ - ... - {mod_service_log, [{loggers, ["bandersnatch.example.com"]}]}, - ... - ]}. +{modules, + [ + ... + {mod_service_log, [{loggers, ["bandersnatch.example.com"]}]}, + ... + ]}.- To log all end user packets to the Bandersnatch service running on bandersnatch.example.com and the backup service on bandersnatch.example.org: -
{modules, - [ - ... - {mod_service_log, [{loggers, ["bandersnatch.example.com", - "bandersnatch.example.org"]}]}, - ... - ]}. -3.3.18 mod_shared_roster
{modules, + [ + ... + {mod_service_log, [{loggers, ["bandersnatch.example.com", + "bandersnatch.example.org"]}]}, + ... + ]}. ++3.3.18 mod_shared_roster
This module enables you to create shared roster groups. This means that you can create groups of people that can see members from (other) groups in their rosters. The big advantages of this feature are that end users do not need to @@ -2581,9 +2529,8 @@ roster groups as shown in the following table:
This module adds support for Statistics Gathering (XEP-0039). This protocol allows you to retrieve next statistics from your ejabberd deployment:
This module features support for Entity Time (XEP-0090). By using this XEP, you are able to discover the time at another entity’s location.
Options:
This module allows end users to store and retrieve their vCard, and to retrieve
other users vCards, as defined in vcard-temp (XEP-0054). The module also
implements an uncomplicated Jabber User Directory based on the vCards of
@@ -2659,28 +2604,27 @@ This option is available in mod_vcard, but not available in mod_vca
In this first situation, search results are limited to twenty items,
every user who added information to their vCard will be listed when people
do an empty search, and only users from the current host will be returned:
- {modules,
- [
- ...
- {mod_vcard, [{search, true},
- {matches, 20},
- {allow_return_all, true},
- {search_all_hosts, false}]},
- ...
- ]}.
+
{modules,
+ [
+ ...
+ {mod_vcard, [{search, true},
+ {matches, 20},
+ {allow_return_all, true},
+ {search_all_hosts, false}]},
+ ...
+ ]}.
{modules,
- [
- ...
- {mod_vcard, [{search, true},
- {matches, infinity},
- {allow_return_all, true}]},
- ...
- ]}.
-
3.3.22 mod_vcard_ldap
{modules, + [ + ... + {mod_vcard, [{search, true}, + {matches, infinity}, + {allow_return_all, true}]}, + ... + ]}. ++
ejabberd can map LDAP attributes to vCard fields. This behaviour is implemented in the mod_vcard_ldap module. This module does not depend on the authentication method (see 3.2.5).
The mod_vcard_ldap module has @@ -2719,44 +2663,44 @@ attributes. The pattern variables "%s" will be sequentially replaced with the values of LDAP attributes from List_of_LDAP_attributes, "%u" will be replaced with the user part of a JID, and "%d" will be replaced with the domain part of a JID. The default is: -
[{"NICKNAME", "%u", []}, - {"FN", "%s", ["displayName"]}, - {"LAST", "%s", ["sn"]}, - {"FIRST", "%s", ["givenName"]}, - {"MIDDLE", "%s", ["initials"]}, - {"ORGNAME", "%s", ["o"]}, - {"ORGUNIT", "%s", ["ou"]}, - {"CTRY", "%s", ["c"]}, - {"LOCALITY", "%s", ["l"]}, - {"STREET", "%s", ["street"]}, - {"REGION", "%s", ["st"]}, - {"PCODE", "%s", ["postalCode"]}, - {"TITLE", "%s", ["title"]}, - {"URL", "%s", ["labeleduri"]}, - {"DESC", "%s", ["description"]}, - {"TEL", "%s", ["telephoneNumber"]}, - {"EMAIL", "%s", ["mail"]}, - {"BDAY", "%s", ["birthDay"]}, - {"ROLE", "%s", ["employeeType"]}, - {"PHOTO", "%s", ["jpegPhoto"]}] +[{"NICKNAME", "%u", []}, + {"FN", "%s", ["displayName"]}, + {"LAST", "%s", ["sn"]}, + {"FIRST", "%s", ["givenName"]}, + {"MIDDLE", "%s", ["initials"]}, + {"ORGNAME", "%s", ["o"]}, + {"ORGUNIT", "%s", ["ou"]}, + {"CTRY", "%s", ["c"]}, + {"LOCALITY", "%s", ["l"]}, + {"STREET", "%s", ["street"]}, + {"REGION", "%s", ["st"]}, + {"PCODE", "%s", ["postalCode"]}, + {"TITLE", "%s", ["title"]}, + {"URL", "%s", ["labeleduri"]}, + {"DESC", "%s", ["description"]}, + {"TEL", "%s", ["telephoneNumber"]}, + {"EMAIL", "%s", ["mail"]}, + {"BDAY", "%s", ["birthDay"]}, + {"ROLE", "%s", ["employeeType"]}, + {"PHOTO", "%s", ["jpegPhoto"]}]
[{"User", "%u"}, - {"Full Name", "displayName"}, - {"Given Name", "givenName"}, - {"Middle Name", "initials"}, - {"Family Name", "sn"}, - {"Nickname", "%u"}, - {"Birthday", "birthDay"}, - {"Country", "c"}, - {"City", "l"}, - {"Email", "mail"}, - {"Organization Name", "o"}, - {"Organization Unit", "ou"}] +[{"User", "%u"}, + {"Full Name", "displayName"}, + {"Given Name", "givenName"}, + {"Middle Name", "initials"}, + {"Family Name", "sn"}, + {"Nickname", "%u"}, + {"Birthday", "birthDay"}, + {"Country", "c"}, + {"City", "l"}, + {"Email", "mail"}, + {"Organization Name", "o"}, + {"Organization Unit", "ou"}]
[{"Full Name", "FN"}, - {"Given Name", "FIRST"}, - {"Middle Name", "MIDDLE"}, - {"Family Name", "LAST"}, - {"Nickname", "NICKNAME"}, - {"Birthday", "BDAY"}, - {"Country", "CTRY"}, - {"City", "LOCALITY"}, - {"Email", "EMAIL"}, - {"Organization Name", "ORGNAME"}, - {"Organization Unit", "ORGUNIT"}] +[{"Full Name", "FN"}, + {"Given Name", "FIRST"}, + {"Middle Name", "MIDDLE"}, + {"Family Name", "LAST"}, + {"Nickname", "NICKNAME"}, + {"Birthday", "BDAY"}, + {"Country", "CTRY"}, + {"City", "LOCALITY"}, + {"Email", "EMAIL"}, + {"Organization Name", "ORGNAME"}, + {"Organization Unit", "ORGUNIT"}]
Examples:
Let’s say ldap.example.org is the name of our LDAP server. We have users with their passwords in "ou=Users,dc=example,dc=org" directory. Also we have addressbook, which contains users emails and their additional infos in "ou=AddressBook,dc=example,dc=org" directory. Corresponding -authentication section should looks like this:
%% authentication method - {auth_method, ldap}. - %% DNS name of our LDAP server - {ldap_servers, ["ldap.example.org"]}. - %% We want to authorize users from 'shadowAccount' object class only - {ldap_filter, "(objectClass=shadowAccount)"}. +authentication section should looks like this:%% authentication method +{auth_method, ldap}. +%% DNS name of our LDAP server +{ldap_servers, ["ldap.example.org"]}. +%% We want to authorize users from 'shadowAccount' object class only +{ldap_filter, "(objectClass=shadowAccount)"}.Now we want to use users LDAP-info as their vCards. We have four attributes defined in our LDAP schema: "mail" — email address, "givenName" — first name, "sn" — second name, "birthDay" — birthday. -Also we want users to search each other. Let’s see how we can set it up:
{modules, - ... - {mod_vcard_ldap, - [ - %% We use the same server and port, but want to bind anonymously because - %% our LDAP server accepts anonymous requests to - %% "ou=AddressBook,dc=example,dc=org" subtree. - {ldap_rootdn, ""}, - {ldap_password, ""}, - %% define the addressbook's base - {ldap_base, "ou=AddressBook,dc=example,dc=org"}, - %% uidattr: user's part of JID is located in the "mail" attribute - %% uidattr_format: common format for our emails - {ldap_uids, [{"mail","%u@mail.example.org"}]}, - %% We have to define empty filter here, because entries in addressbook does not - %% belong to shadowAccount object class - {ldap_filter, ""}, - %% Now we want to define vCard pattern - {ldap_vcard_map, - [{"NICKNAME", "%u", []}, % just use user's part of JID as his nickname - {"FIRST", "%s", ["givenName"]}, - {"LAST", "%s", ["sn"]}, - {"FN", "%s, %s", ["sn", "givenName"]}, % example: "Smith, John" - {"EMAIL", "%s", ["mail"]}, - {"BDAY", "%s", ["birthDay"]}]}, - %% Search form - {ldap_search_fields, - [{"User", "%u"}, - {"Name", "givenName"}, - {"Family Name", "sn"}, - {"Email", "mail"}, - {"Birthday", "birthDay"}]}, - %% vCard fields to be reported - %% Note that JID is always returned with search results - {ldap_search_reported, - [{"Full Name", "FN"}, - {"Nickname", "NICKNAME"}, - {"Birthday", "BDAY"}]} - ]} - ... - }. +Also we want users to search each other. Let’s see how we can set it up:{modules, + ... + {mod_vcard_ldap, + [ + %% We use the same server and port, but want to bind anonymously because + %% our LDAP server accepts anonymous requests to + %% "ou=AddressBook,dc=example,dc=org" subtree. + {ldap_rootdn, ""}, + {ldap_password, ""}, + %% define the addressbook's base + {ldap_base, "ou=AddressBook,dc=example,dc=org"}, + %% uidattr: user's part of JID is located in the "mail" attribute + %% uidattr_format: common format for our emails + {ldap_uids, [{"mail","%u@mail.example.org"}]}, + %% We have to define empty filter here, because entries in addressbook does not + %% belong to shadowAccount object class + {ldap_filter, ""}, + %% Now we want to define vCard pattern + {ldap_vcard_map, + [{"NICKNAME", "%u", []}, % just use user's part of JID as his nickname + {"FIRST", "%s", ["givenName"]}, + {"LAST", "%s", ["sn"]}, + {"FN", "%s, %s", ["sn", "givenName"]}, % example: "Smith, John" + {"EMAIL", "%s", ["mail"]}, + {"BDAY", "%s", ["birthDay"]}]}, + %% Search form + {ldap_search_fields, + [{"User", "%u"}, + {"Name", "givenName"}, + {"Family Name", "sn"}, + {"Email", "mail"}, + {"Birthday", "birthDay"}]}, + %% vCard fields to be reported + %% Note that JID is always returned with search results + {ldap_search_reported, + [{"Full Name", "FN"}, + {"Nickname", "NICKNAME"}, + {"Birthday", "BDAY"}]} + ]} + ... +}.Note that mod_vcard_ldap module checks an existence of the user before searching his info in LDAP.
{ldap_vcard_map, - [{"NICKNAME", "%u", []}, - {"FN", "%s", ["displayName"]}, - {"CTRY", "Russia", []}, - {"EMAIL", "%u@%d", []}, - {"DESC", "%s\n%s", ["title", "description"]} - ]}, +{ldap_vcard_map, + [{"NICKNAME", "%u", []}, + {"FN", "%s", ["displayName"]}, + {"CTRY", "Russia", []}, + {"EMAIL", "%u@%d", []}, + {"DESC", "%s\n%s", ["title", "description"]} + ]},
{ldap_search_fields, - [{"User", "uid"}, - {"Full Name", "displayName"}, - {"Email", "mail"} - ]}, +{ldap_search_fields, + [{"User", "uid"}, + {"Full Name", "displayName"}, + {"Email", "mail"} + ]},
{ldap_search_reported, - [{"Full Name", "FN"}, - {"Email", "EMAIL"}, - {"Birthday", "BDAY"}, - {"Nickname", "NICKNAME"} - ]}, -
{ldap_search_reported, + [{"Full Name", "FN"}, + {"Email", "EMAIL"}, + {"Birthday", "BDAY"}, + {"Nickname", "NICKNAME"} + ]}, ++
This module implements Software Version (XEP-0092). Consequently, it answers ejabberd’s version when queried.
Options:
Options: The default value is true.
The ejabberdctl command line administration script allows to start, stop and perform +
+The ejabberdctl command line administration script allows to start, stop and perform many other administrative tasks in a local or remote ejabberd server.
When ejabberdctl is executed without any parameter, it displays the available options. If there isn’t an ejabberd server running, the available parameters are: @@ -2900,9 +2841,8 @@ error is represented by 1, and other codes may be used for specifical results. This can be used by other scripts to determine automatically if a command succedded or failed, -for example using: echo $?
-ejabberd is an Erlang/OTP application that runs inside an Erlang runtime system. +for example using: echo $?
+ejabberd is an Erlang/OTP application that runs inside an Erlang runtime system. This system is configured using environment variables and command line parameters. The ejabberdctl administration script uses many of those possibilities. You can configure some of them with the file ejabberdctl.cfg, @@ -2968,9 +2908,8 @@ Starts the Erlang system detached from the system console. Open an Erlang shell in a remote Erlang node.
Note that some characters need to be escaped when used in shell scripts, for instance "
and {}
.
-You can find other options in the Erlang manual page (erl -man erl).
- +You can find other options in the Erlang manual page (erl -man erl).
+The ejabberd Web Admin allows to administer most of ejabberd using a web browser.
This feature is enabled by default: a ejabberd_http listener with the option web_admin (see section 3.1.3) is included in the listening ports. Then you can open @@ -2979,7 +2918,7 @@ will be asked to enter the username (the full Jabber ID) and password of an ejabberd user with administrator rights. After authentication you will see a page similar to figure 4.1.
- +