Bug in xmlns for grantowner and grantadmin / not in sync with JEP-0045


Gajim/Tkabber can neither grant owner nor admin privileges, yet JBother can. Having a look at at the code send, the reason becomes obvious.

For owner the following does not work:

Yet JBother, which is based on smack, works because it sends the following to wildfire:

http://www.jabber.org/jeps/jep-0045.html#grantowner states that http://jabber.org/protocol/muc#owner has to be ...#admin, even for granting owner privileges and the bare JID should be used, i.e. no /Miranda. The latter might be a JBother bug, or a smack bug. If it is necessary though in order for the server to execute the command it is a wildfire bug too. "Affiliations are granted, revoked, and maintained based on the user's bare JID." (http://www.jabber.org/jeps/jep-0045.html#affil)

Same for requesting the admin-list or granting admin-privileges:

http://www.jabber.org/jeps/jep-0045.html#grantadmin states that is should be http://jabber.org/protocol/muc#admin instead of #owner and the bare JID should be used.




Guus der Kinderen
May 18, 2012, 7:34 PM

Florians patch was applied to Openfire.

Florian Schmaus
May 2, 2012, 7:20 PM

of-98.patch: Allow MUC owner/admin changes and listings from the muc#admin namespace. Stays backwards compatible.

Florian Schmaus
April 21, 2012, 11:32 PM

This issue should be linked with SMACK-371. I think openfire can easily be changed to accept both muc#admin and muc#owner for owner and admin listing/changes, therefore remaining backwards compatible. A first try from me can be seen here: https://github.com/Flowdalic/openfire/commit/99c1ac9f2b7dc57f300031b2710f2f414efde2a0

Daryl Herzmann
February 17, 2009, 4:49 AM

bumping up to next release for consideration / comment

Sven B.
February 6, 2007, 3:30 AM

This bug was filed almost a year ago and makes it impossible to admin MUC for all clients but those that use the buggy libs provided for spark. So this is important for all other clients that support MUC.

The changes mentioned as a reason to postpone the fix of this bug have nothing to do with this bug, i.e. the part of the JEP that is related to this bug did not change and hence it is not an excuse to not fix this issue.

The bug report clearly states the bug and how to fix it. It is a matter of replacing #owner by #admin.

Sorry, but over a year to get something as important as MUC administration right is too long to sustain any kind of motivation to even file bugs, which is a pain anyway.

Based on the assumption that replacing two strings, takes less time than adapting to some more small changes in a XEP, how long is this going to take? Even more than one year? What if the JEP changes again, another year?

It might seem a bit harsh, but you cannot expect people to use wildfire and tell their MUC admins to switch clients everytime they want to do some admin-stuff. This is not a feature request or some fancy niche-bug, it was an obvious xmlns-bug and still is. Now, because waiting that long, it got company, which is taken as a reason to postpone it again. Not even to 3.2.1 or 3.3 but 3.x.

Your pinned fields
Click on the next to a field label to start pinning.


Guus der Kinderen