Mercurial > sat_docs
annotate xmpp/xep-proto-privileged-component.xml @ 37:2abfd0f6fd34
association: AG extraordinaire du 05/02/2015
| author | souliane <souliane@mailoo.org> |
|---|---|
| date | Thu, 05 Feb 2015 11:46:12 +0100 |
| parents | 175434d8ed5a |
| children |
| rev | line source |
|---|---|
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
1 <?xml version='1.0' encoding='UTF-8'?> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
2 <!DOCTYPE xep SYSTEM 'xep.dtd' [ |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
3 <!ENTITY % ents SYSTEM 'xep.ent'> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
4 %ents; |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
5 ]> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
6 <?xml-stylesheet type='text/xsl' href='xep.xsl'?> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
7 <xep> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
8 <header> |
| 17 | 9 <title>privileged entity</title> |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
10 <abstract>This specification provides a way for XMPP entities to have a privileged access to some other entities data</abstract> |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
11 <legal> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
12 <copyright>This XMPP Extension Protocol is copyright (c) 1999 - 2014 by the XMPP Standards Foundation (XSF).</copyright> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
13 <permissions>Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the "Specification"), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation.</permissions> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
14 <warranty>## NOTE WELL: This Specification is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. In no event shall the XMPP Standards Foundation or the authors of this Specification be liable for any claim, damages, or other liability, whether in an action of contract, tort, or otherwise, arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification. ##</warranty> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
15 <liability>In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising out of the use or inability to use the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages.</liability> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
16 <conformance>This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which may be found at <<link url='http://xmpp.org/extensions/ipr-policy.shtml'>http://xmpp.org/extensions/ipr-policy.shtml</link>> or obtained by writing to XSF, P.O. Box 1641, Denver, CO 80201 USA).</conformance> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
17 </legal> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
18 <number>xxxx</number> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
19 <status>ProtoXEP</status> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
20 <type>Standards Track</type> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
21 <sig>Standards</sig> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
22 <approver>Council</approver> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
23 <dependencies> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
24 <spec>XMPP Core</spec> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
25 </dependencies> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
26 <supersedes/> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
27 <supersededby/> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
28 <shortname>NOT_YET_ASSIGNED</shortname> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
29 <author> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
30 <firstname>Jérôme</firstname> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
31 <surname>Poisson</surname> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
32 <email>goffi@goffi.org</email> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
33 <jid>goffi@jabber.fr</jid> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
34 </author> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
35 <revision> |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
36 <version>0.0.4</version> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
37 <date>2014-12-18</date> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
38 <initials>jp</initials> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
39 <remark><ul> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
40 <li>Big simplification and restriction following council's veto and standard@ discussions</li> |
|
35
e4ed0682d7b6
XEP: fixed a typo in privileged entity
Goffi <goffi@goffi.org>
parents:
34
diff
changeset
|
41 <li>Configuration is now done only on server own configuration</li> |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
42 <li>No more client mode</li> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
43 <li>Permissions are adverised using &MESSAGE;</li> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
44 <li>The only &IQ; privilege still available is jabber:iq:roster</li> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
45 </ul> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
46 </remark> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
47 </revision> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
48 <revision> |
| 31 | 49 <version>0.0.3</version> |
| 50 <date>2014-11-13</date> | |
| 51 <initials>jp</initials> | |
| 52 <remark><ul> | |
| 53 <li>giving permission to manage this XEP namespace is forbidden</li> | |
| 54 <li>Added configuration section; with well-defined command node</li> | |
| 55 <li>better specification of persistent permissions</li> | |
| 56 <li>fixed erroneous example (server returns bookmarks)</li> | |
| 57 <li>added special permissions</li> | |
| 58 <li>better specification of &QUERY; element</li> | |
| 59 </ul> | |
| 60 </remark> | |
| 61 </revision> | |
| 62 <revision> | |
| 17 | 63 <version>0.0.2</version> |
| 64 <date>2014-09-17</date> | |
| 65 <initials>jp</initials> | |
| 66 <remark><ul> | |
| 67 <li>changed for privileged entity</li> | |
| 68 <li>fixes after feedbacks on standard mailing list</li> | |
| 69 <li>completed missing required parts</li> | |
| 70 </ul> | |
| 71 </remark> | |
| 72 </revision> | |
| 73 <revision> | |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
74 <version>0.0.1</version> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
75 <date>2014-05-09</date> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
76 <initials>jp</initials> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
77 <remark><p>First draft.</p></remark> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
78 </revision> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
79 </header> |
| 31 | 80 |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
81 <section1 topic='Introduction' anchor='intro'> |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
82 <p>XMPP components are used for long through &xep0114;, but are quite limited: they have a restricted access to other entities data, similar to what a client can do. This is sufficient for components like gateways, but very limiting for more complex components like a PubSub service. The goal of this XEP is to allow a component or any entity to have a "privileged" status, and access some other entity data with the same privileges than the entity itself, that means manage an entity roster on its behalf, send &MESSAGE; or receive &PRESENCE; stanzas in the name of the server.</p> |
| 32 | 83 <p>Privileged entities have numerous advantages, including:</p> |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
84 <ul> |
| 17 | 85 <li>a step forward in decentralization: it is possible for an entity to do tasks which were before reserved to server itself. For example, a privileged pubsub component can offer access model based on publisher's roster</li> |
| 86 <li>better integration of components: a gateway can add items to an entity roster itself</li> | |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
87 <li>possibility to overpass a server limitation (typically: incomplete PEP implementation)</li> |
| 17 | 88 <li>quick development cycle: developers can implement the components they need without waiting for a new server release</li> |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
89 <li>server agnostic</li> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
90 </ul> |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
91 <p>Privileged entity has been created with the main goal to create an external, server agnostic, PEP service. It is restricted to only a couple of features, see <link url='#acks'>Acknowledgements section</link> for more details</p> |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
92 </section1> |
| 31 | 93 |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
94 <section1 topic='Requirements' anchor='reqs'> |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
95 <p>A privileged entity must be able to do what a PEP service can do and to access roster, so it must be able to (according to configuration):</p> |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
96 <ul> |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
97 <li>get and modify the roster of any entity managed by the server</li> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
98 <li>send a &MESSAGE; stanza on behalf of the server</li> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
99 <li>access &PRESENCE; informations for entities in a managed entity's roster (and for managed entity itself)</li> |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
100 </ul> |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
101 <p>The privilege mechanism MUST be totally transparent for the managed entities.</p> |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
102 </section1> |
| 31 | 103 |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
104 <section1 topic='Glossary' anchor='glossary'> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
105 <ul> |
| 32 | 106 <li><strong>Privileged entity</strong> — the entity which has a privileged status.</li> |
| 107 <li><strong>Managed entity</strong> — the entity that is managed by a privileged entity.</li> | |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
108 </ul> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
109 </section1> |
| 31 | 110 |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
111 <section1 topic='Accessing roster' anchor='access_roster'> |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
112 |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
113 <section2 topic='Server Allows Roster Access' anchor='server_roster'> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
114 <p>Roster access is granted in the server configuration. Roster access can have 4 types:</p> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
115 <ul> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
116 <li><strong>none</strong> — the entity is not allowed to access managed entity roster at all. This MUST be the default value.</li> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
117 <li><strong>get</strong> — the entity is allowed to send &IQ; stanzas of type <em>'get'</em> for the namespace 'jabber:iq:roster'.</li> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
118 <li><strong>set</strong> — the entity is allowed to send &IQ; stanzas of type <em>'set'</em> for namespace 'jabber:iq:roster'.</li> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
119 <li><strong>both</strong> — the entity is allowed to send &IQ; stanzas of type <em>'get'</em> and <em>'set'</em> for namespace 'jabber:iq:roster'.</li> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
120 </ul> |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
121 </section2> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
122 |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
123 <section2 topic='Server Advertise Entity Of Allowed Permission' anchor='advertise_roster'> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
124 <p>Once an entity is authenticated and stream is started, the server send it a &MESSAGE; stanza with a <privilege> elements which MUST have the namespace 'urn:xmpp:privilege:0'. This element contains <perm> elements which MUST contain a 'namespace' attribute of the value "jabber:iq:roster" and a 'type' attribute which must correspond to the type configured as specified in <link url='#server_roster'>"Server Allows Roster Access" section</link></p> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
125 <example caption='Server Advertise Roster Privilege'><![CDATA[ |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
126 <message from='capulet.net' to='pubub.capulet.lit' id='12345'> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
127 <privilege xmlns='urn:xmpp:privilege:0'> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
128 <perm namespace='jabber:iq:roster' type='both'/> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
129 </privilege> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
130 </message> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
131 ]]></example> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
132 <p>Here <em>pubsub.capulet.lit</em> is allowed to do <em>get</em> and <em>set</em> operations on all entities managed by capulet.lit</p> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
133 </section2> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
134 |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
135 <section2 topic='Privileged Entity Manage Roster' anchor='priv_manage_roster'> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
136 <p>Doing a <em>get</em> or <em>set</em> operation on the roster of a managed entity is done in the usual way (as described in &rfc6121; section 2), except that the 'to' attribute is set to the attribute of the managed entity. The server MUST check that the privileged entity has right to <em>get</em> or <em>set</em> the roster of managed entity, and MUST return a &forbidden; error if it is not the case:</p> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
137 <example caption='Privileged Entity Get Managed Entity Roster'><![CDATA[ |
| 17 | 138 <iq id='roster1' |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
139 from='pubsub.capulet.lit' |
| 17 | 140 to='juliet@example.com' |
| 141 type='get' | |
| 142 id='roster1'> | |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
143 <query xmlns='jabber:iq:roster'/> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
144 </iq> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
145 ]]></example> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
146 |
| 32 | 147 <p>The server then answers normally, as it would have done to the managed entity:</p> |
| 148 <example caption='Server Answers To Privileged Entity'><![CDATA[ | |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
149 <iq id='roster1' |
| 31 | 150 from='juliet@example.com' |
| 17 | 151 to='pubsub.capulet.net' |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
152 type='result'> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
153 <query xmlns='jabber:iq:roster' ver='ver7'> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
154 <item jid='nurse@example.com'/> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
155 <item jid='romeo@example.net'/> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
156 </query> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
157 </iq> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
158 ]]></example> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
159 |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
160 </section2> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
161 </section1> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
162 |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
163 <section1 topic='Message Permission' anchor='message'> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
164 <section2 topic='Authorizing Messages' anchor='auth_mess'> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
165 <p>In some cases, it can be desirable to send notifications (e.g. PEP service), so the privileged entity must be able to send &MESSAGE; stanzas. This is allowed in server configuration in the same way as for roster permission. The permission type can have the following values:</p> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
166 <ul> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
167 <li><strong>none</strong> — the entity is not allowed to send &MESSAGE; stanza in the name of the server. This MUST be the default value.</li> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
168 <li><strong>outgoing</strong> — the entity is allowed to send &MESSAGE; stanzas in the name of the server, according to following restrictions.</li> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
169 </ul> |
| 32 | 170 <p>A privileged entity can then send message on the behalf either of the server or of a bare JID of the server, using &xep0297;, with the following restrictions:</p> |
| 31 | 171 <ol> |
| 172 <li>forwarded &MESSAGE; 'type' attribute has the value of "headline"</li> | |
| 32 | 173 <li>forwarded &MESSAGE; 'from' attribute MUST be a bare JID from the server, no resource is allowed</li> |
| 31 | 174 </ol> |
| 175 <p>If any of this rules is violated, the server MUST return a <not-authorized/> stream error and close the connection, as explained in &rfc6120; section 4.9.3.12.</p> | |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
176 </section2> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
177 |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
178 <section2 topic='Advertising Permission' anchor='advertise_mess'> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
179 <p>Server advertise "message" permission in the same way as for "roster" permission, except that 'namespace' attribute has the value of "message", and the 'type' attribute as a value of 'outgoing':</p> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
180 <example caption='Server Advertise Roster And Message Privileges'><![CDATA[ |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
181 <message from='capulet.net' to='pubub.capulet.lit' id='54321'> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
182 <privilege xmlns='urn:xmpp:privilege:0'> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
183 <perm namespace='jabber:iq:roster' type='both'/> |
| 31 | 184 <perm namespace='message' type='outgoing'/> |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
185 </privilege> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
186 </message> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
187 ]]></example> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
188 </section2> |
| 31 | 189 |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
190 <section2 topic='Sending messages' anchor='sending_mess'> |
| 31 | 191 <p>Now that <em>pubsub.capulet.lit</em> is allowed, it can send messages using <forwarded/> elements.</p> |
| 192 <example caption='privileged entity send a notificaction message'><![CDATA[ | |
| 193 <message from='pubsub.capulet.lit' to='capulet.lit' id='notif1'> | |
| 194 <forwarded xmlns='urn:xmpp:forward:0'> | |
| 195 <message from='juliet@capulet.lit' | |
| 196 id='foo' | |
| 197 to='romeo@montague.lit/orchard' | |
| 198 type='headline' | |
| 199 xmlns='jabber:client'> | |
| 200 <event xmlns='http://jabber.org/protocol/pubsub#event'> | |
| 201 <items node='http://jabber.org/protocol/tune'> | |
| 202 <item> | |
| 203 <tune xmlns='http://jabber.org/protocol/tune'> | |
| 204 <artist>Gerald Finzi</artist> | |
| 205 <length>255</length> | |
| 206 <source>Music for "Love's Labors Lost" (Suite for small orchestra)</source> | |
| 207 <title>Introduction (Allegro vigoroso)</title> | |
| 208 <track>1</track> | |
| 209 </tune> | |
| 210 </item> | |
| 211 </items> | |
| 212 </event> | |
| 213 <delay xmlns='urn:xmpp:delay' stamp='2014-11-25T14:34:32Z'/> | |
| 214 </message> | |
| 215 </forwarded> | |
| 216 </message> | |
| 217 ]]></example> | |
| 32 | 218 <p>The server sees that forwarded message type is '<em>headline</em>', that <em>juliet@capulet.lit</em> is a bare JID of the server, and that outgoing message permission was granted in admin mode (so all bare JIDs from server are allowed); it can now send the notification:</p> |
| 219 <example caption='server sends the notification as if it was originating from him'><![CDATA[ | |
| 31 | 220 <message from='juliet@capulet.lit' |
| 221 id='bar' | |
| 222 to='romeo@montague.lit/orchard' | |
| 223 type='headline'> | |
| 224 <event xmlns='http://jabber.org/protocol/pubsub#event'> | |
| 225 <items node='http://jabber.org/protocol/tune'> | |
| 226 <item> | |
| 227 <tune xmlns='http://jabber.org/protocol/tune'> | |
| 228 <artist>Gerald Finzi</artist> | |
| 229 <length>255</length> | |
| 230 <source>Music for "Love's Labors Lost" (Suite for small orchestra)</source> | |
| 231 <title>Introduction (Allegro vigoroso)</title> | |
| 232 <track>1</track> | |
| 233 </tune> | |
| 234 </item> | |
| 235 </items> | |
| 236 </event> | |
| 237 <delay xmlns='urn:xmpp:delay' stamp='2014-11-25T14:34:32Z'/> | |
| 238 </message> | |
| 239 ]]></example> | |
| 240 </section2> | |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
241 </section1> |
| 31 | 242 |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
243 <section1 topic='Presence Permission' anchor='presence'> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
244 <section2 topic='Managed Entity Presence' anchor='managed_ent_presence'> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
245 <p>It can be often desirable for a privileged entity to have presence information of the managed entities (e.g. to know when to send them notificiations). As privileges must be transparent for the managed entity, this presence has to be sent by the server without modifying managed entity roster.</p> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
246 <p>This is allowed in server configuration in the same way as for <em>roster</em> and <em>message</em> permissions. The "presence" type can have the following values:</p> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
247 <ul> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
248 <li><strong>none</strong> — the entity is not allowed to access &PRESENCE; informations at all. This MUST be the default value.</li> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
249 <li><strong>managed_entity</strong> — the entity is allowed to receive managed entity presence (see below).</li> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
250 <li><strong>roster</strong> — the entity is allowed to receive presence informations of managed entity contacts, see <link url='#roster_presence'>Roster Presence section</link>.</li> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
251 </ul> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
252 <p>If the privilege is granted, the server MUST use a directed presence, as specified in &rfc6121; section 4.6 on the behalf of managed entity each time its presence information change.</p> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
253 </section2> |
| 31 | 254 |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
255 <section2 topic='Advertising Permission' anchor='advertise_managed_presence'> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
256 <p>Server advertise "presence" permission in the same way as for "roster" or "message" permissions, except that 'namespace' attribute has the value of "presence", and the 'type' attribute has a value of "managed_entity"</p> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
257 </section2> |
| 31 | 258 |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
259 <section2 topic="Server Send presence informations" anchor='server_send_presence'> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
260 <p>Once the "presence" permission is granted, the server send presence informations:</p> |
| 32 | 261 <example caption='server receives new presence from Juliet'><![CDATA[ |
| 31 | 262 <presence from='juliet@capulet.lit/balcony' |
| 263 id='presence1' | |
| 264 xml:lang='en'> | |
| 265 <show>chat</show> | |
| 266 <status>Staying on the balcony</status> | |
| 267 </presence> | |
| 268 ]]></example> | |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
269 |
| 32 | 270 <example caption='server redirects presence to privileged entity'><![CDATA[ |
| 31 | 271 <presence from='juliet@capulet.lit/balcony' |
| 272 to='pubsub.capulet.lit' | |
| 273 id='presence1' | |
| 274 xml:lang='en'> | |
| 275 <show>chat</show> | |
| 276 <status>Staying on the balcony</status> | |
| 277 </presence> | |
| 278 ]]></example> | |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
279 |
| 31 | 280 </section2> |
| 281 | |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
282 <section2 topic='Roster Presence' anchor='roster_presence'> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
283 <p>In addition to "<link url='#managed_ent_presence'>managed entity presence</link>", a privileged entity may need to know when a contact in managed entity roster is online (for example, it's necessary for a PEP service because of the presence default access model).</p> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
284 <p>As for other permissions, the access in granted in server's configuration, but there is a additional restriction: the privileged entity MUST have read permission on roster namespace (i.e. 'type' attribute in allowed <perm> of namespace <em>jabber:iq:roster</em> MUST have a value of either <strong>get</strong> or <strong>both</strong>).</p> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
285 <p>If the delegation is granted, the server MUST send to the privileged entity every presence information that the privileged entity is receiving. Having "roster" type for "presence" permission imply that you have also implicitly "managed_entity" type.</p><p>The server MUST reject the permission if the privileged entity doesn't have read permission on roster namespace.</p> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
286 <p>Note: this permission should be given carefully, as it gives access to presence of potentially a lot of entities to the privileged entity (see <link url='#security'>security considerations</link>).</p> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
287 </section2> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
288 |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
289 <section2 topic='Advertising Permission' anchor='advertise_roster_presence'> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
290 <p>Server advertise roster "presence" permission in the same way as for other permissions, except that the 'namespace' attribute has the value of "presence", and the 'type' attribute has a value of "roster"</p> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
291 <example caption='Server Advertise Roster, Message, Managed Entity Presence and Roster Presence Privileges'><![CDATA[ |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
292 <message from='capulet.net' to='pubub.capulet.lit' id='54321'> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
293 <privilege xmlns='urn:xmpp:privilege:0'> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
294 <perm namespace='jabber:iq:roster' type='both'/> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
295 <perm namespace='message'/> |
| 31 | 296 <perm namespace='presence' type='roster'/> |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
297 </privilege> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
298 </message> |
| 31 | 299 ]]></example> |
| 300 <p>Note the presence of <em>jabber:iq:roster</em> permission request.</p> | |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
301 </section2> |
| 31 | 302 |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
303 <section2 topic="Privileged Entity Receive Roster Presences" anchor='priv_rec_roster_presence'> |
| 32 | 304 <example caption="server receives new presence from Romeo, which is in Juliet's roster"><![CDATA[ |
| 31 | 305 <presence from='romeo@montaigu.lit/orchard'/> |
| 306 ]]></example> | |
| 32 | 307 <example caption='server sends the presence as usually, but also to the privileged entity'><![CDATA[ |
| 31 | 308 <presence from='romeo@montaigu.lit/orchard' |
| 309 to='juliet@capulet.lit'/> | |
| 310 <presence from='romeo@montaigu.lit/orchard' | |
| 311 to='pubsub.capulet.lit'/> | |
| 312 ]]></example> | |
| 313 </section2> | |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
314 </section1> |
| 31 | 315 |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
316 <section1 topic='Security Considerations' anchor='security'> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
317 <ol> |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
318 <li>Privileged entitiy has access to sensitive data, and can act as the server itself, permissions should be granted carefuly, only if you absolutely trust the entity.</li> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
319 <li><link url='#roster_presence'>Roster presence</link> is particulary sensitive, because presence informations of whole rosters are shared.</li> |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
320 </ol> |
|
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
321 </section1> |
| 31 | 322 |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
323 <section1 topic='IANA Considerations' anchor='iana'> |
| 17 | 324 <p>This document requires no interaction with &IANA;.</p> |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
325 </section1> |
| 31 | 326 |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
327 <section1 topic='XMPP Registrar Considerations' anchor='registrar'> |
| 17 | 328 <section2 topic='Protocol Namespaces' anchor='ns'> |
| 329 <p>The ®ISTRAR; includes 'urn:xmpp:privilege:0' in its registry of protocol namespaces (see &NAMESPACES;).</p> | |
| 330 <ul> | |
| 331 <li>urn:xmpp:privilege:0</li> | |
| 332 </ul> | |
| 333 </section2> | |
| 334 <section2 topic='Protocol Versioning' anchor='registrar-versioning'> | |
| 335 &NSVER; | |
| 336 </section2> | |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
337 </section1> |
| 31 | 338 |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
339 <section1 topic='XML Schema' anchor='schema'> |
| 17 | 340 <code><![CDATA[ |
| 341 <?xml version='1.0' encoding='UTF-8'?> | |
| 342 | |
| 343 <xs:schema | |
| 344 xmlns:xs='http://www.w3.org/2001/XMLSchema' | |
| 345 targetNamespace='urn:xmpp:privilege:0' | |
| 346 xmlns='urn:xmpp:privilege:0' | |
| 347 elementFormDefault='qualified'> | |
| 348 | |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
349 <xs:element name='privilege'> |
| 17 | 350 <xs:complexType> |
| 351 <xs:element name='perm' | |
| 352 maxOccurs='unbounded'> | |
| 353 <xs:complexType> | |
| 354 <xs:attribute name='namespace' use='required' type='xs:string'/> | |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
355 <xs:simpleType base='xs:NMTOKEN'> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
356 <xs:enumeration value='jabber:iq:roster'/> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
357 <xs:enumeration value='message'/> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
358 <xs:enumeration value='presence'/> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
359 </xs:simpleType> |
| 17 | 360 <xs:attribute name='type' use='required'> |
| 361 <xs:simpleType base='xs:NMTOKEN'> | |
| 362 <xs:enumeration value='none'/> | |
| 363 <xs:enumeration value='get'/> | |
| 364 <xs:enumeration value='set'/> | |
| 365 <xs:enumeration value='both'/> | |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
366 <xs:enumeration value='outgoing'/> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
367 <xs:enumeration value='managed_entity'/> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
368 <xs:enumeration value='roster'/> |
| 17 | 369 </xs:simpleType> |
| 370 </xs:attribute> | |
| 371 </xs:complexType> | |
| 372 </xs:element> | |
| 373 </xs:complexType> | |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
374 </xs:element> |
| 17 | 375 |
| 376 </xs:schema> | |
| 377 ]]></code> | |
| 378 </section1> | |
| 31 | 379 |
| 17 | 380 <section1 topic='Acknowledgements' anchor='acks'> |
|
33
b70084aa0af7
xeps: added thanks to souliane for his corrections
Goffi <goffi@goffi.org>
parents:
32
diff
changeset
|
381 <p>Thanks to Sergey Dobrov, Dave Cridland, Steven Lloyd Watkin, Lance Stout and Johannes Hund for their feedbacks. Thanks to Adrien Cossa for his typos/style corrections.</p> |
|
34
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
382 <p>Privileged entity was initialy written to be a generic identity based access control (IBAC) which allows an entity to access sensitive data. After <link url='http://mail.jabber.org/pipermail/standards/2014-December/029378.html'>a discussion on standard mailing list</link>, it has been decided to restrict the current XEP to immediate needs to build an external PEP service, and to implement separately an Attribute Based Access Control (ABAC) which is more modern, generic and flexible. This XEP is still interesting for being easy to implement and doing the job.</p> |
|
db9316a75306
XEP: updated privileged entity according to discussions following the council's veto (see http://mail.jabber.org/pipermail/standards/2014-December/029378.html):
Goffi <goffi@goffi.org>
parents:
33
diff
changeset
|
383 |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
384 </section1> |
| 31 | 385 |
|
0
677de998f9d9
XMPP: added privileged component protoXEP
Goffi <goffi@goffi.org>
parents:
diff
changeset
|
386 </xep> |