On 11/23/09 8:08 AM, Ilya Braude wrote: > Adriano Bonat wrote: >> On Fri, Nov 20, 2009 at 12:58 PM, Peter Saint-Andre >> <[email protected]> wrote: >> >>> On 11/19/09 8:42 PM, Adriano Bonat wrote: >>> >>> >>>> trying to subscribe user >>>> "test1" using the user "admin". >>>> >>> That's not going to work, at least not if you're trying to do something >>> like this: >>> >>> <iq type='set' >>> from='[email protected]/foo' >>> to='pubsub.example.net' >>> id='sub1'> >>> <pubsub xmlns='http://jabber.org/protocol/pubsub'> >>> <subscribe >>> node='bar' >>> jid='[email protected]'/> >>> </pubsub> >>> </iq> >>> >>> How is pubsub.example.net supposed to know that [email protected] is >>> authorized to subscribe [email protected] to the node? >>> >>> I think Fritzy meant that your application would add test1 behind the >>> scenes (not via protocol) >>> >>> >> >> From the spec: >> http://xmpp.org/extensions/xep-0060.html#subscriber-subscribe-error-nomatch >> >> >> "[...] those entities may be considered "trusted proxies" that are >> allowed to subscribe on behalf of other entities" >> >> I will send an email to some ejabberd mailing list to check if there >> is a way to configure that. >> > > What about the #owner part of the spec? > http://xmpp.org/extensions/xep-0060.html#owner-subscriptions-modify > > You can have the user who created the pubsub node (or other configured > owners) modify subscription states for any other jid.
Yes, that is one possible approach. In any given deployment, the "trusted proxy" could always be a node owner. Note that there are security implications here -- we don't necessarily want just anyone to be able to subscribe entities to nodes (that's why email discussion lists require confirmation!). Peter -- Peter Saint-Andre https://stpeter.im/
smime.p7s
Description: S/MIME Cryptographic Signature
