What I don't understand: after we switch from default authentication to ejabberd_auth_http, does ejabberd still use and maintain its internal Mnesia database with users?

If you look at ejabberd_auth_http.erl exported functions, none of them provides the list of accounts. I see the same results as with using ejabberd_auth_http: I can log in, but cannot get the list of users. I tried to use an external script written in C# as ejabberd authentication method instead. What if I implement necessary REST points like register, remove_user for ejabberd_auth_http to use? Would Mnesia user storage still be maintained by ejabberd? If not, then how could the list of registered users be obtained? I don't see that ejabberd_auth_http provides an API for getting user list or XEP-0055: Jabber Search. So, persistence mechanism like Mnesia or SQL should work regardless of using ejabberd_auth_http, that's what you're saying? What I don't understand: after we switch from default authentication to ejabberd_auth_http, does ejabberd still use and maintain its internal Mnesia database with, in #266 you said, 'you can use an authentication method (mnesia, sql, external script, whatever), and configure the modules to use whatever storage method you want.' 17:19:10.017 Supervisor ejabberd_http_sup had child undefined started with in ejabberd_auth_http:make_req/5 line 225 Sometimes (but not always, I couldn't get any pattern) ejabberd logs show error / crash related to ejabberd_auth_http: Apparently they cannot access the list of registered users if auth_method: http. Now, neither web admin console nor ejabberdctl registered_users shows registered users anymore.

When I open ejabberd web admin console I see that a break point inside check_password is hit. I created a simple Web Api app with a controller which two GET methods listening on Path_prefix: '/services/imd35000/api/v1/ejabberd/'

Default ejabberd admin password