ejabberd - Comments for "Manual Entry into the routing table?"

This doesn't work. Basically,

saurabha — Thu, 12 Feb 2009 11:38:52 +0000

This doesn't work. Basically, I looked at the erl code, and the access control is happening inside the ejabberd_service and is based on the "from" attribute, and not on the "to" attribute.

Also, on failure, it returns an error "405 not allowed" instead of seeing if there is anything else to route to.

Any other ideas.

Thanks for your reply - let

saurabha — Tue, 10 Feb 2009 09:48:13 +0000

Thanks for your reply - let me try it and see if it works.

access can be on the "to" id - i though acls were for "from" id.

Just an idea

mfoss — Mon, 09 Feb 2009 19:35:25 +0000

So you currently have this?

{listen,
 [
  ...
  {5231, ejabberd_service, [{hosts, ["domain.com"], [{password, "somesecret"}]}]},
  ...
 ]
}.

The only idea that I can think is the Access option, but I don't know if it will work at all:

{acl, user1, {user, "user1", "domain.com"}}.
{acl, user2, {user, "user2", "domain.com"}}.

{access, onlyuser1, [{allow, user1}, {deny, all}]}.
{access, onlyuser2, [{allow, user2}, {deny, all}]}.

{listen,
 [
  ...
  {5231, ejabberd_service, [{access, onlyuser1}, {hosts, ["domain.com"], [{password, "somesecret"}]}]},
  {5232, ejabberd_service, [{access, onlyuser2}, {hosts, ["domain.com"], [{password, "somesecret"}]}]},
  ...
 ]
}.