ejabberd_c2s - Serves client connections to the server.

There are four services (or modules) in total: The next step is to bind ejabberd services to TCP ports and configure those services. I will use the web interface only for viewing, not for editing settings, so let all settings be taken from the file - clear everything: override_acls - only permissions parameters.override_local - parameters of the current node (server) only.override_global - global parameters affecting all nodes in the cluster (what a cluster is, at first, is not very important).The first step is to indicate which part of the configuration (stored in the database) we want to change. The initial setting is done by editing the file /usr/local/etc/ejabberd/ejabberd.cfg. Parameters are specified something like this: Understanding this will save a lot of time, nerves and scalp hair.Ī little about the syntax of configuration filesĬomments begin with a% character and end at the end of the line. Changes made to the config file may not affect the ejabberd config.Changes made via the web interface may be lost when restarting ejabberd.There are two important conclusions to be drawn from this: configuration files rewrite information in the database, but not all, but only the specified part (which - see below about override_XXX).configuration files are read only once at ejabberd start.the web interface changes data only in the database.ejabberd uses the configuration recorded in the database.There is also a web interface for management. DB with the current configuration (/var/spool/ejabberd/).It is important to understand how ejabberd works with settings. You can read about installing on other systems in the ejabberd Guide. I installed ejabberd from FreeBSD ports without any difficulty.

ejabberd 1.1.4_2 (the latest version in FreeBSD ports at the time of installation)Īll paths indicated in the note are specific to FreeBSD, on other systems they may be different. LDAP server at (our servers are connected to the local network company.local) There are several sites on the server, including the site of our company with the domain (so as not to be accused of self-promotion - the name has been changed :-) And since we actively use LDAP, it seemed logical to use it for user authentication and account management. To communicate with others, to organize a secure and independent messaging system, I decided to set up a corporate jabber server. However, not all of my employees have a Jabber account (not everyone even knows what it is :-), which makes communication at work somewhat difficult. Taking the opportunity, I set up my own Jabber server, which I use with success to this day. I parted with ICQ a long time ago and without regrets.

Ejabberd ldap