Hello, I am setting ODBC(mysql) database for ejabbed.
Though I wanted to use both registered user in odbc and anonymous users, I could not find a way to do it.
I tried several configuration but all of them does not work well. I can use both internal and anonymous, but not combination of odbc and anonymous.
If someone know how to deal with both ODBC user and anonymous user, I am very happy to hear the solution :)
Here is several settings of ejabberd.yml which fails. (I am using ejabbed15.11 and mysql 5.6 on ubuntu)
(1)
auth_method: odbc host_config: "myhostname.example.com": auth_method: anonymous anonymous_protocol: both allow_multiple_connections: true
(2)
auth_method: odbc host_config: "myhostname.example.com": auth_method: - odbc - anonymous anonymous_protocol: both allow_multiple_connections: true
(3)
auth_method: odbc auth_method: anonymous anonymous_protocol: both allow_multiple_connections: true
(4)
host_config: "myhostname.example.com": auth_method: - odbc - anonymous anonymous_protocol: both allow_multiple_connections: true
Thank you very much !
Then I tested several
Then I tested several settings with several versions of ejabberd.
With ejabberd15.04, I succeeded login both users in mysql db and anonymous users with following setting in ejabbed.yml:
---------------------------------------
auth_method: odbc
host_config:
"mydomain.example.com":
auth_method:
- odbc
- anonymous
anonymous_protocol: both
allow_multiple_connections: true
---------------------------------------
However, for ejabberd15.11 with same setting, I could not succeeded login with users in mysql db. (anonymous login was succeeded.)
I am very happy if someone can advise me.
I also tested with following
I also tested with following ejabbed versions: 15.04, .06, .07, .09, .10, .11.
.04 and .06 are OK for both login (odbc:mysql and anonymous), but .07, .09, .10, .11 are only anonymous login available.
You are right. I've
You are right. I've investigated a little further the problem, and reported it here:
https://github.com/processone/ejabberd/issues/886
For now, the only solution is to copy an old ejabberd_config.erl to new ejabberd, like this:
https://raw.githubusercontent.com/processone/ejabberd/76104cd117126a2ac8...
In case you wonder, the correct config is (4), or more simply: