ejabberd - Comments for "Allowing in-channel registration from a specific IP"

The provided example does not

mremond — Wed, 07 Oct 2015 16:54:10 +0000

The provided example does not allow anyone to register. From what I see, it is tight to loopback. Only user connected on local machine can register. So it is probably more secured that you wish. You need to adapt to your case.

Thanks, but that's not quite

verandaguy — Tue, 06 Oct 2015 19:50:29 +0000

Thanks, but that's not quite what I'm looking for.

I don't want to allow logged-in users on non-whitelisted networks to be able to register. Say someone logs into an existing account from the public Wi-Fi at a mall or an airport, I don't want to allow everyone on that network to register.

(Based on my test, this does let anyone from a network with a logged-in client create an account, even from separate clients).

Using ejabberd 15.07 and this

badlop — Thu, 24 Sep 2015 15:50:55 +0000

Using ejabberd 15.07 and this configuration, a client already logged in can register another account:

acl:
  loopback:
    ip:
      - "127.0.0.0/8"
      - "::1"

access:
  mynetworks:
    loopback: allow
    all: deny

modules:
  mod_register:
    ip_access: mynetworks
    access_from: register
    access: register

sent:
<iq id='96:885601'
	type='set'
	to='localhost'>
  <query xmlns='jabber:iq:register'>
    <username>user1234</username>
    <password>somepass</password>
    <registered/>
  </query>
</iq>
received:
<iq from='localhost'
	to='asdaADS2323@localhost/tka1'
	id='96:885601'
	type='result'/>