OK, I figured out that the

deceze — Tue, 29 Nov 2011 09:37:54 +0000

OK, I figured out that the component was not registering itself correctly. In order for it to be invoked, it needs to hook into the right events and it needs to announce its ability in the protocol, otherwise clients will not even try to call it. This is the current setup:

start(Host, Ops) ->
    ejabberd_hooks:add(c2s_stream_features, Host, ?MODULE, stream_feature_register, 50),
    ejabberd_hooks:add(c2s_unauthenticated_iq, Host, ?MODULE, on_c2s_unauthenticated_iq, 50),
    ...
%% Without this, clients won't know about the availability of the registration feature
stream_feature_register(Acc, _Host) -> [{ xmlelement, "register", [{ "xmlns", ?NS_FEATURE_IQREGISTER }], [] } | Acc].
on_c2s_unauthenticated_iq(_Acc, Server, #iq{ type = get, xmlns = ?NS_REGISTER } = IQ, IP) -> registration_format_iq(Server, IQ, IP);
on_c2s_unauthenticated_iq(_Acc, Server, #iq{ type = set, xmlns = ?NS_REGISTER } = IQ, IP) -> registration_iq(Server, IQ, IP).
%% Announce the required registration form fields
registration_format_iq(Server, IQ, IP) ->
    jlib:iq_to_xml(IQ#iq{ type = result, sub_el = [
        { xmlelement, "query", [{ "xmlns", ?NS_REGISTER }], [
            { xmlelement, "instructions", [], [{ xmlcdata, "These are my custom registration fields." }] },
            { xmlelement, "email", [], [] },
            { xmlelement, "phone", [], [] }
        ] }
    ] }).
registration_iq(Server, #iq{ sub_el = SubEl } = IQ, IP) ->
    %% Handle actual registration...

When the original mod_registration is disabled, this works fine.

ejabberd - Comments for "Developing a custom registration module"

OK, I figured out that the