MUC service not announced in disco items/info #413

Closed
opened 2022-05-31 09:27:22 +00:00 by raucao · 1 comment
Owner

I found out that the reason that the XMPP compliance test suite is currently reporting we don't support MUC, despite our daily use of it, is that the MUC items are missing from the service discovery info.

This also means that if you don't already have that service info cached, people cannot e.g. create private chat rooms, because there is no MUC domain/service that the client can find with normal discovery (as reported by @maxsan).

I think the reason is that the MUC config is included in a separate modules block via include_config_file and append_host_config and there seems to be a subtle bug in how ejabberd then assembles the service info from the config.

Edit: We should first upgrade to 22.05 to see if that was already fixed, and if not, then report the bug upstream. Still happening with the latest release version.

I found out that the reason that the [XMPP compliance test suite](https://compliance.conversations.im/server/kosmos.org/) is currently reporting we don't support MUC, despite our daily use of it, is that the MUC items are missing from the service discovery info. This also means that if you don't already have that service info cached, people cannot e.g. create private chat rooms, because there is no MUC domain/service that the client can find with normal discovery (as reported by @maxsan). I think the reason is that the MUC config is included in a separate modules block via `include_config_file` and `append_host_config` and there seems to be a subtle bug in how ejabberd then assembles the service info from the config. Edit: <del>We should first upgrade to 22.05 to see if that was already fixed, and if not, then report the bug upstream.</del> Still happening with the latest release version.
raucao added the
service
xmpp
bug
labels 2022-05-31 09:27:22 +00:00
raucao added a new dependency 2022-05-31 09:27:57 +00:00
raucao added this to the Current operational issues project 2022-05-31 09:31:28 +00:00
Author
Owner
Reported here: https://github.com/processone/ejabberd/issues/3836
greg closed this issue 2022-06-11 09:16:24 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Depends on
Reference: kosmos/chef#413
No description provided.