Lindsay Oproman wrote: > Hello, I apologize for the lag. I have been away on vacation. All I > really want is for authorization of a topic to apply to any full JID > associated with an authorized bare JID. The notifications should only > go to resources that have explicitly subscribed using their full JID. > > For example, [EMAIL PROTECTED] is authorized to a topic. I don't want the > publisher to have to authorize [EMAIL PROTECTED]/resource1 or > [EMAIL PROTECTED]/resource2 thereafter. However, suppose > [EMAIL PROTECTED]/resource2 has not subscribed to the topic. That resource > should not receive a notification. > > It is my understanding that the current authorization mode requires > the publisher to manually authorize each resource individually.
If the node is configured for an access model of "authorize" then each subscription request will need to be approved by the node owner, unless the implementation includes some logic to pre-approve subscription requests from all resources based on the bare JID ([EMAIL PROTECTED]). (Sounds like a good feature request.) If the node is configured for an access model of "open", "presence", "roster", or "whitelist", then no authorization is needed from the node owner for a subscription request. So you can subscribe multiple times, once from each resource (in some cases you need to be on an implicit authorization list via presence subscription or whatever). Are you specifically asking about the "authorize" access model? Peter -- Peter Saint-Andre https://stpeter.im/
smime.p7s
Description: S/MIME Cryptographic Signature
