ejabberd 2.0.1 (rereleased) - Bugfixes, R12, PubSub, registration limit

Update: the original release didn't include all the files. Make sure to download a file that includes the suffix "_2": ejabberd-2.0.1_2
source package does not include the correct files. It will be fixed today and I'll update this newspost.

ejabberd 2.0.1 revision has been released. It has been three months since the first release in the 2.0.x line.

The main changes are:

  • Erlang/OTP R12B-2 support.
  • Better LDAP handling.
  • PubSub bugfixes.
  • Documentation improvements.
  • In-band registration limitation per IP.
  • S2S improvement.
A detailed list of fixed issues is available at the ejabberd bugtracker at Process-one support site.

For official downloads go to the ejabberd download page.

If you are using ejabberd 2.0.0 it is recommended to update to 2.0.1. The 2.0.x release line is expected to receive another revision with minor bugfixes (see ejabberd 2.0.2 plan).

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Win2000Server (CZ) -

Win2000Server (CZ) - instalator not run

LDAP authentication with AD

On the linux version there seems to be an bug with ldap authentication with Active directory, user needs to be part of user group "USERS" to get authenticated. With the 2.0 version user need not be member of group "USERS" to get authenticated. tried testing with the windows version, but seems that the windows installer has an bug, on my laptop with vista i am getting beam_smp.dll not found.

Cannot replicate your USERS group problem

Anonymous wrote:

On the linux version there seems to be an bug with ldap authentication with Active directory, user needs to be part of user group "USERS" to get authenticated. With the 2.0 version user need not be member of group "USERS" to get authenticated.

I attempted to replicate this problem using LDAP server.

I tried with ejabberd trunk SVN and also with ejabberd 2.0.1 Linux x86 binary installer. I have a user in a test LDAP server, in the organisational unit 'People', and can login correctly.

In addition I checked changes in ejabberd source code between 2.0.0 and 2.0.1, and there isn't any change where "USERS" is mentioned.

Are you sure it is a bug in ejabberd, and not somewhere else, for example some option in ejabberd.cfg? If you still think it's a bug, do you have any idea why it works for me using LDAP?

AD user group: bug tracked

Anonymous wrote:

On the linux version there seems to be an bug with ldap authentication with Active directory, user needs to be part of user group "USERS" to get authenticated. With the 2.0 version user need not be member of group "USERS" to get authenticated.

Thanks, I've reported it in the bug tracker: Users need to be in AD group "USERS"

It needs some investigation

Anonymous wrote:

On the linux version there seems to be an bug with ldap authentication with Active directory, user needs to be part of user group "USERS" to get authenticated. With the 2.0 version user need not be member of group "USERS" to get authenticated.

I'll investigate this in the next days.

Anonymous wrote:

tried testing with the windows version, but seems that the windows installer has an bug, on my laptop with vista i am getting beam_smp.dll not found.

Thanks for the report. The problem is tracked here: SMP support on Windows. There is also a temporary solution so you can use it in the meantime.

Syndicate content