Bug Report -- Pub Sub (XEP-0060)

Openfire Openfire Dev
1

Openfire (Version 3.8.2)

Let me first of all commend the developers of (and contributors to) Openfire for their effort and dedication.

Bug 1?

**
**

In Section 5.6 of XEP-0060, a request -reply (IQ) exchange associated with retrieving subscription information of a PubSub node is described in examples 24 and 25.

The get IQ is a follows;

<iq type='get'
 from='francisco@denmark.lit/barracks'
 to='pubsub.shakespeare.lit'
 id='subscriptions2'>
 <pubsub xmlns='[http://jabber.org/protocol/pubsub](http://jabber.org/protocol/pubsub)'>
 <subscriptions node='node6'/>
 </pubsub>
 </iq>

And the result IQ should be thus;




<subscription node=‘node6’ jid=‘francisco@denmark.lit’

subscription=‘subscribed’ subid=‘123-abc’/>
<subscription node=‘node6’ jid=‘francisco@denmark.lit’

subscription='subscribed' subid='004-yyy'/>
 </subscriptions>

However, Openfire 3.8.2 returns the following ;




<subscription jid=‘francisco@denmark.lit’

subscription='subscribed' subid='123-abc'/>
   <subscription jid='francisco@denmark.lit'

subscription='subscribed' subid='004-yyy'/>
 </subscriptions>

The ’ node’ attribute of the ‘subscription’ element is missing. Is this deliberate?

Bug 2?

Examples 30 and 31 of the same section associated with Retrieving node affiliation i.e.,

<iq type='get'
 from='francisco@denmark.lit/barracks'
 to='pubsub.shakespeare.lit'
 id='affil2'>
 <pubsub xmlns='[http://jabber.org/protocol/pubsub](http://jabber.org/protocol/pubsub)'>
 <affiliations node='node6'/>
 </pubsub>
 </iq>

<iq type='result'
 from='pubsub.shakespeare.lit'
 to='francisco@denmark.lit'
 id='affil2'>
 <pubsub xmlns='[http://jabber.org/protocol/pubsub](http://jabber.org/protocol/pubsub)'>
 <affiliations>
 <affiliation node='node6' affiliation='owner'/>
 </affiliations>
 </pubsub>
 </iq>

Openfire 3.8.2 returns the following IQ result

<iq type='result'
 from='pubsub.shakespeare.lit'
 to='francisco@denmark.lit'
 id='affil1'>
 <pubsub xmlns='[http://jabber.org/protocol/pubsub](http://jabber.org/protocol/pubsub)'>
 <affiliations>
 <affiliation node='node1' affiliation='owner'/>
 <affiliation node='node2' affiliation='publisher'/>
 <affiliation node='node5' affiliation='outcast'/>
 <affiliation node='node6' affiliation='owner'/>
 </affiliations>
 </pubsub>
 </iq>

Specifically, it returns the affiliation of all nodes present in the pub sub service as opposed to those associated with the specific node ( as dictated by the XEP). In my opinion, this bug will make it quite tedious to query affiliations in nodes that are nested in other nodes.

Many thanks for taking out time to read this.

Kind regards,

Fizachi

1 Like