draft-ietf-webdav-acl-09.txt   draft-ietf-webdav-acl-10.txt 
INTERNET-DRAFT Geoffrey Clemm, Rational Software INTERNET-DRAFT Geoffrey Clemm, IBM
draft-ietf-webdav-acl-09 Anne Hopkins, Microsoft Corporation draft-ietf-webdav-acl-10 Anne Hopkins, Microsoft Corporation
Eric Sedlar, Oracle Corporation Eric Sedlar, Oracle Corporation
Jim Whitehead, U.C. Santa Cruz Jim Whitehead, U.C. Santa Cruz
Expires January 26, 2003 July 26, 2002 Expires September 15, 2003 March 15, 2003
WebDAV Access Control Protocol WebDAV Access Control Protocol
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions of
Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other groups
may also distribute working documents as Internet-Drafts.
This document is an Internet-Draft and is subject to all provisions
of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference time. It is inappropriate to use Internet- Drafts as reference material
material or to cite them other than as "work in progress." or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract Abstract
This document specifies a set of methods, headers, message bodies, This document specifies a set of methods, headers, message bodies,
properties, and reports that define Access Control extensions to the properties, and reports that define Access Control extensions to the
WebDAV Distributed Authoring Protocol. This protocol permits a client WebDAV Distributed Authoring Protocol. This protocol permits a client to
to read and modify access control lists that instruct a server read and modify access control lists that instruct a server whether to
whether to allow or deny operations upon a resource (such as allow or deny operations upon a resource (such as HyperText Transfer
HyperText Transfer Protocol (HTTP) method invocations) by a given Protocol (HTTP) method invocations) by a given principal. A lightweight
principal. A lightweight representation of principals as Web representation of principals as Web resources supports integration of a
resources supports integration of a wide range of user management wide range of user management repositories. Search operations allow
repositories. Search operations allow discovery and manipulation of discovery and manipulation of principals using human names.
principals using human names.
This document is a product of the Web Distributed Authoring and This document is a product of the Web Distributed Authoring and
Versioning (WebDAV) working group of the Internet Engineering Task Versioning (WebDAV) working group of the Internet Engineering Task
Force. Comments on this draft are welcomed, and should be addressed Force. Comments on this draft are welcomed, and should be addressed to
to the acl@webdav.org mailing list. Other related documents can be the acl@webdav.org mailing list. Other related documents can be found at
found at http://www.webdav.org/acl/, and http://www.example.com/acl/, and
http://www.ics.uci.edu/pub/ietf/webdav/. http://www.ics.uci.edu/pub/ietf/webdav/.
Clemm, Hopkins, Sedlar, Whitehead [Page 1] Clemm, et al. [Page 1]
Table of Contents Table of Contents
1 INTRODUCTION....................................................4 WEBDAV ACCESS CONTROL PROTOCOL............................1
1.1 Terms.........................................................7
1.2 Notational Conventions........................................8
2 PRINCIPALS......................................................8 STATUS OF THIS MEMO.......................................1
3 PRIVILEGES......................................................9 ABSTRACT..................................................1
3.1 DAV:read Privilege...........................................10
3.2 DAV:write Privilege..........................................10
3.3 DAV:write-properties.........................................10
3.4 DAV:write-content............................................11
3.5 DAV:unlock...................................................11
3.6 DAV:read-acl Privilege.......................................12
3.7 DAV:read-current-user-privilege-set Privilege................12
3.8 DAV:write-acl Privilege......................................12
3.9 DAV:all Privilege............................................12
3.10 Aggregation of Predefined Privileges........................12
4 PRINCIPAL PROPERTIES...........................................13 TABLE OF CONTENTS.........................................2
4.1 DAV:alternate-URI-set........................................14
4.2 DAV:principal-URL............................................14
4.3 DAV:group-member-set.........................................14
4.4 DAV:group-membership.........................................14
5 ACCESS CONTROL PROPERTIES......................................15 1 INTRODUCTION...........................................4
5.1 DAV:owner....................................................15 1.1 Terms.................................................6
5.1.1 Example: Retrieving DAV:owner............................15 1.2 Notational Conventions................................7
5.1.2 Example: An Attempt to Set DAV:owner.....................16
5.2 DAV:supported-privilege-set..................................17 2 PRINCIPALS.............................................7
5.2.1 Example: Retrieving a List of Privileges Supported on a
Resource.......................................................18 3 PRIVILEGES.............................................8
5.3 DAV:current-user-privilege-set...............................20 3.1 DAV:read Privilege....................................9
3.2 DAV:write Privilege...................................9
3.3 DAV:write-properties.................................10
3.4 DAV:write-content....................................10
3.5 DAV:unlock...........................................10
3.6 DAV:read-acl Privilege...............................11
3.7 DAV:read-current-user-privilege-set Privilege........11
3.8 DAV:write-acl Privilege..............................11
3.9 DAV:delete Privilege.................................11
3.10 DAV:all Privilege..................................11
3.11 Aggregation of Predefined Privileges...............12
4 PRINCIPAL PROPERTIES..................................12
4.1 DAV:alternate-URI-set................................12
4.2 DAV:principal-URL....................................13
4.3 DAV:group-member-set.................................13
4.4 DAV:group-membership.................................13
5 ACCESS CONTROL PROPERTIES.............................13
5.1 DAV:owner............................................14
5.1.1 Example: Retrieving DAV:owner....................14
5.1.2 Example: An Attempt to Set DAV:owner.............15
5.2 DAV:supported-privilege-set..........................16
5.2.1 Example: Retrieving a List of Privileges Supported on a Resource
16
5.3 DAV:current-user-privilege-set.......................19
5.3.1 Example: Retrieving the User's Current Set of Assigned 5.3.1 Example: Retrieving the User's Current Set of Assigned
Privileges.....................................................21 Privileges..............................................19
5.4 DAV:acl......................................................22 5.4 DAV:acl..............................................20
5.4.1 ACE Principal............................................22 5.4.1 ACE Principal....................................20
5.4.2 ACE Grant and Deny.......................................24 5.4.2 ACE Grant and Deny...............................21
5.4.3 ACE Protection...........................................24 5.4.3 ACE Protection...................................22
5.4.4 ACE Inheritance..........................................24 5.4.4 ACE Inheritance..................................22
5.4.5 Example: Retrieving a Resource's Access Control List.....25 5.4.5 Example: Retrieving a Resource's Access Control List 22
5.5 DAV:acl-semantics............................................26 5.5 DAV: acl-restrictions................................24
5.5.1 Example: Retrieving DAV:acl-semantics....................27 5.5.1 DAV:grant-only...................................24
5.6 DAV:inherited-acl-set........................................28
5.7 DAV:principal-collection-set.................................28
5.7.1 Example: Retrieving DAV:principal-collection-set.........29
5.8 Example: PROPFIND to retrieve access control properties......30
Clemm, Hopkins, Sedlar, Whitehead [Page 2] Clemm, et al. [Page 2]
6 ACL SEMANTICS..................................................34 5.5.2 DAV:no-invert ACE Constraint.....................24
6.1 ACE Combination..............................................34 5.5.3 DAV:deny-before-grant............................24
6.1.1 DAV:first-match ACE Combination..........................34 5.5.4 Required Principals..............................24
6.1.2 DAV:all-grant-before-any-deny ACE Combination............34 Example: Retrieving DAV:acl-restrictions................25
6.1.3 DAV:specific-deny-overrides-grant ACE Combination........35 5.6 DAV:inherited-acl-set................................26
6.2 ACE Ordering.................................................35 5.7 DAV:principal-collection-set.........................26
6.2.1 DAV:deny-before-grant ACE Ordering.......................35 5.7.1 Example: Retrieving DAV:principal-collection-set.27
6.3 Allowed ACE..................................................35 5.8 Example: PROPFIND to retrieve access control properties28
6.3.1 DAV:principal-only-one-ace ACE Constraint................35
6.3.2 DAV:grant-only ACE Constraint............................35
6.3.3 DAV:no-invert ACE Constraint.............................36
6.4 Required Principals..........................................36
7 ACCESS CONTROL AND EXISTING METHODS............................36 6 ACL EVALUATION........................................31
7.1 OPTIONS......................................................36
7.1.1 Example - OPTIONS........................................36
7.2 MOVE.........................................................37
7.3 COPY.........................................................37
7.4 DELETE.......................................................37
7.5 LOCK.........................................................37
8 ACCESS CONTROL METHODS.........................................37 7 ACCESS CONTROL AND EXISTING METHODS...................32
8.1 ACL..........................................................37 7.1 OPTIONS..............................................32
8.1.1 ACL Preconditions........................................38 7.1.1 Example - OPTIONS................................32
8.1.2 Example: the ACL method..................................40 7.2 MOVE.................................................33
8.1.3 Example: ACL method failure due to protected ACE 7.3 COPY.................................................33
conflict ................................................41 7.4 LOCK.................................................33
8.1.4 Example: ACL method failure due to an inherited ACE
conflict ................................................42
8.1.5 Example: ACL method failure due to an attempt to set
grant and deny in a single ACE ..........................43
9 ACCESS CONTROL REPORTS.........................................44 8 ACCESS CONTROL METHODS................................33
9.1 REPORT Method................................................44 8.1 ACL..................................................33
9.2 DAV:acl-principal-prop-set Report............................44 8.1.1 ACL Preconditions................................34
9.2.1 Example: DAV:acl-principal-prop-set Report...............45 8.1.2 Example: the ACL method..........................35
9.3 DAV:principal-match REPORT...................................46 8.1.3 Example: ACL method failure due to protected ACE conflict 36
9.3.1 Example: DAV:principal-match REPORT......................48 8.1.4 Example: ACL method failure due to an inherited ACE conflict 37
9.4 DAV:principal-property-search REPORT.........................48 8.1.5 Example: ACL method failure due to an attempt to set grant and
9.4.1 Matching.................................................51 deny in a single ACE....................................38
9.4.2 Example: successful DAV:principal-property-search REPORT 51
9.4.3 Example: Unsuccessful DAV:principal-property-search
REPORT ..................................................53
9.5 DAV:principal-search-property-set REPORT.....................54
9.5.1 Example: DAV:principal-search-property-set REPORT........56
10 XML PROCESSING...............................................57 9 ACCESS CONTROL REPORTS................................39
9.1 REPORT Method........................................39
9.2 DAV:acl-principal-prop-set Report....................40
9.2.1 Example: DAV:acl-principal-prop-set Report.......41
9.3 DAV:principal-match REPORT...........................42
9.3.1 Example: DAV:principal-match REPORT..............43
9.4 DAV:principal-property-search REPORT.................44
9.4.1 Matching.........................................46
9.4.2 Example: successful DAV:principal-property-search REPORT 46
9.4.3 Example: Unsuccessful DAV:principal-property-search REPORT 48
9.5 DAV:principal-search-property-set REPORT.............49
9.5.1 Example: DAV:principal-search-property-set REPORT50
11 INTERNATIONALIZATION CONSIDERATIONS..........................57 10 XML PROCESSING.......................................51
Clemm, Hopkins, Sedlar, Whitehead [Page 3] 11 INTERNATIONALIZATION CONSIDERATIONS..................51
12 SECURITY CONSIDERATIONS......................................58
12.1 Increased Risk of Compromised Users.........................58 12 SECURITY CONSIDERATIONS..............................52
12.1 Increased Risk of Compromised Users................52
12.2 Risks of the DAV:read-acl and DAV:current-user-privilege-set 12.2 Risks of the DAV:read-acl and DAV:current-user-privilege-set
Privileges.......................................................58 Privileges...............................................53
12.3 No Foreknowledge of Initial ACL.............................59 12.3 No Foreknowledge of Initial ACL....................53
13 AUTHENTICATION...............................................59 13 AUTHENTICATION.......................................54
14 IANA CONSIDERATIONS..........................................60 14 IANA CONSIDERATIONS..................................54
15 INTELLECTUAL PROPERTY........................................60 Clemm, et al. [Page 3]
15 INTELLECTUAL PROPERTY................................54
16 ACKNOWLEDGEMENTS.............................................60 16 ACKNOWLEDGEMENTS.....................................55
17 REFERENCES...................................................61 17 REFERENCES...........................................55
17.1 Normative References........................................61 17.1 Normative References...............................55
17.2 Informational References....................................61 17.2 Informational References...........................56
18 AUTHORS' ADDRESSES...........................................62 18 AUTHORS' ADDRESSES...................................57
19 APPENDICES...................................................63 19 APPENDICES...........................................58
19.1 WebDAV XML Document Type Definition Addendum................63 19.1 WebDAV XML Document Type Definition Addendum.......58
19.2 WebDAV Method Privilege Table (Normative)..........60
1 INTRODUCTION 1 INTRODUCTION
The goal of the WebDAV access control extensions is to provide an The goal of the WebDAV access control extensions is to provide an
interoperable mechanism for handling discretionary access control interoperable mechanism for handling discretionary access control
for content and metadata managed by WebDAV servers. WebDAV access for content and metadata managed by WebDAV servers. WebDAV access
control can be implemented on content repositories with security as control can be implemented on content repositories with security as
simple as that of a UNIX file system, as well as more sophisticated simple as that of a UNIX file system, as well as more sophisticated
models. The underlying principle of access control is that who you models. The underlying principle of access control is that who you
are determines what operations you can perform on a resource. The are determines what operations you can perform on a resource. The
skipping to change at line 196 skipping to change at line 197
ACE specifies a principal and a set of privileges that are either ACE specifies a principal and a set of privileges that are either
granted or denied to that principal. When a principal submits an granted or denied to that principal. When a principal submits an
operation (such as an HTTP or WebDAV method) to a resource for operation (such as an HTTP or WebDAV method) to a resource for
execution, the server evaluates the ACEs in the ACL to determine if execution, the server evaluates the ACEs in the ACL to determine if
the principal has permission for that operation. the principal has permission for that operation.
Since every ACE contains the identifier of a principal, client Since every ACE contains the identifier of a principal, client
software operated by a human must provide a mechanism for selecting software operated by a human must provide a mechanism for selecting
this principal. This specification uses http(s) scheme URLs to this principal. This specification uses http(s) scheme URLs to
identify principals, which are represented as WebDAV-capable identify principals, which are represented as WebDAV-capable
Clemm, Hopkins, Sedlar, Whitehead [Page 4]
resources. There is no guarantee that the URLs identifying resources. There is no guarantee that the URLs identifying
principals will be meaningful to a human. For example, principals will be meaningful to a human. For example,
http://www.dav.org/u/256432 and http://www.example.com/u/256432 and
http://www.dav.org/people/Greg.Stein are both valid URLs that could http://www.example.com/people/Greg.Stein are both valid URLs that
be used to identify the same principal. To remedy this, every could be used to identify the same principal. To remedy this, every
principal resource has the DAV:displayname property containing a principal resource has the DAV:displayname property containing a
human-readable name for the principal. human-readable name for the principal.
Since a principal can be identified by multiple URLs, it raises the Since a principal can be identified by multiple URLs, it raises the
problem of determining exactly which principal is being referenced problem of determining exactly which principal is being referenced
in a given ACE. It is impossible for a client to determine that an in a given ACE. It is impossible for a client to determine that an
ACE granting the read privilege to ACE granting the read privilege to
http://www.dav.org/people/Greg.Stein also affects the principal at http://www.example.com/people/Greg.Stein also affects the principal
http://www.dav.org/u/256432. That is, a client has no mechanism for at http://www.example.com/u/256432. That is, a client has no
determining that two URLs identify the same principal resource. As mechanism for determining that two URLs identify the same principal
a result, this specification requires clients to use just one of
the many possible URLs for a principal when creating ACEs. A client Clemm, et al. [Page 4]
can discover which URL to use by retrieving the DAV:principal-URL resource. As a result, this specification requires clients to use
property (Section 4.2) from a principal resource. No matter which just one of the many possible URLs for a principal when creating
of the principal's URLs is used with PROPFIND, the property always ACEs. A client can discover which URL to use by retrieving the
returns the same URL. DAV:principal-URL property (Section 4.2) from a principal resource.
No matter which of the principal's URLs is used with PROPFIND, the
property always returns the same URL.
With a system having hundreds to thousands of principals, the With a system having hundreds to thousands of principals, the
problem arises of how to allow a human operator of client software problem arises of how to allow a human operator of client software
to select just one of these principals. One approach is to use to select just one of these principals. One approach is to use
broad collection hierarchies to spread the principals over a large broad collection hierarchies to spread the principals over a large
number of collections, yielding few principals per collection. An number of collections, yielding few principals per collection. An
example of this is a two level hierarchy with the first level example of this is a two level hierarchy with the first level
containing 36 collections (a-z, 0-9), and the second level being containing 36 collections (a-z, 0-9), and the second level being
another 36, creating collections /a/a/, /a/b/, ..., /a/z/, such another 36, creating collections /a/a/, /a/b/, ..., /a/z/, such
that a principal with last name "Stein" would appear at /s/t/Stein. that a principal with last name "Stein" would appear at /s/t/Stein.
skipping to change at line 247 skipping to change at line 248
This specification provides the capability to perform substring This specification provides the capability to perform substring
searches over a small set of properties on the resources searches over a small set of properties on the resources
representing principals. This permits searches based on last name, representing principals. This permits searches based on last name,
first name, user name, job title, etc. Two separate searches are first name, user name, job title, etc. Two separate searches are
supported, both via the REPORT method, one to search principal supported, both via the REPORT method, one to search principal
resources (DAV:principal-property-search, Section 9.4), the other resources (DAV:principal-property-search, Section 9.4), the other
to determine which properties may be searched at all to determine which properties may be searched at all
(DAV:principal-search-property-set, Section 9.5). (DAV:principal-search-property-set, Section 9.5).
Clemm, Hopkins, Sedlar, Whitehead [Page 5]
Once a principal has been identified in an ACE, a server evaluating Once a principal has been identified in an ACE, a server evaluating
that ACE must know the identity of the principal making a protocol that ACE must know the identity of the principal making a protocol
request, and must validate that that principal is who they claim to request, and must validate that that principal is who they claim to
be, a process known as authentication. This specification be, a process known as authentication. This specification
intentionally omits discussion of authentication, as the HTTP intentionally omits discussion of authentication, as the HTTP
protocol already has a number of authentication mechanisms protocol already has a number of authentication mechanisms
[RFC2617]. Some authentication mechanism (such as HTTP Digest [RFC2617]. Some authentication mechanism (such as HTTP Digest
Authentication, which all WebDAV compliant implementations are Authentication, which all WebDAV compliant implementations are
required to support) must be available to validate the identity of required to support) must be available to validate the identity of
a principal. a principal.
The following issues are out of scope for this document: The following issues are out of scope for this document:
* Access control that applies only to a particular property on a Access control that applies only to a particular property on a
resource (excepting the access control properties DAV:acl and resource (excepting the access control properties DAV:acl and
DAV:current-user-privilege-set), rather than the entire DAV:current-user-privilege-set), rather than the entire resource,
resource,
* Role-based security (where a role can be seen as a dynamically Role-based security (where a role can be seen as a dynamically
defined group of principals), defined group of principals),
* Specification of the ways an ACL on a resource is initialized, Clemm, et al. [Page 5]
Specification of the ways an ACL on a resource is initialized,
* Specification of an ACL that applies globally to all Specification of an ACL that applies globally to all resources,
resources, rather than to a particular resource. rather than to a particular resource.
* Creation and maintenance of resources representing people or Creation and maintenance of resources representing people or
computational agents (principals), and groups of these. computational agents (principals), and groups of these.
This specification is organized as follows. Section 1.1 defines key This specification is organized as follows. Section 1.1 defines key
concepts used throughout the specification, and is followed by a concepts used throughout the specification, and is followed by a
more in-depth discussion of principals (Section 2), and privileges more in-depth discussion of principals (Section 2), and privileges
(Section 3). Properties defined on principals are specified in (Section 3). Properties defined on principals are specified in
Section 4, and access control properties for content resources are Section 4, and access control properties for content resources are
specified in Section 5. The semantics of access control lists are specified in Section 5. The ways ACLs are to be evaluated is
described in Section 6, including sections on ACE combination described in section 6. Client discovery of access control
(Section 6.1), ACE ordering (Section 6.2), and principals required capability using OPTIONS is described in Section 7.1. Interactions
to be present in an ACE (Section 6.3.2). Client discovery of access between access control functionality and existing HTTP and WebDAV
control capability using OPTIONS is described in Section 7.1. methods are described in the remainder of Section 7. The access
Interactions between access control functionality and existing HTTP control setting method, ACL, is specified in Section 8. Four
and WebDAV methods are described in the remainder of Section 7. The
access control setting method, ACL, is specified in Section 8. Four
reports that provide limited server-side searching capabilities are reports that provide limited server-side searching capabilities are
described in Section 9. Sections on XML processing (Section 10), described in Section 9. Sections on XML processing (Section 10),
Internationalization considerations (Section 11), security Internationalization considerations (Section 11), security
considerations (Section 12), and authentication (Section 13) round considerations (Section 12), and authentication (Section 13) round
out the specification. An appendix (Section 19.1) provides an XML out the specification. An appendix (Section 19.1) provides an XML
Document Type Definition (DTD) for the XML elements defined in the Document Type Definition (DTD) for the XML elements defined in the
specification. specification.
Clemm, Hopkins, Sedlar, Whitehead [Page 6]
1.1 Terms 1.1 Terms
This draft uses the terms defined in HTTP [RFC2616] and WebDAV This draft uses the terms defined in HTTP [RFC2616] and WebDAV
[RFC2518]. In addition, the following terms are defined: [RFC2518]. In addition, the following terms are defined:
principal principal
A "principal" is a distinct human or computational actor that A "principal" is a distinct human or computational actor that
initiates access to network resources. In this protocol, a initiates access to network resources. In this protocol, a
principal is an HTTP resource that represents such an actor. principal is an HTTP resource that represents such an actor.
group group
A "group" is a principal that represents a set of other principals. A "group" is a principal that represents a set of other principals.
privilege privilege
A "privilege" controls access to a particular set of HTTP A "privilege" controls access to a particular set of HTTP
operations on a resource. operations on a resource.
aggregate privilege aggregate privilege
An "aggregate privilege" is a privilege that contains a set of An "aggregate privilege" is a privilege that contains a set of
other privileges. other privileges.
abstract privilege abstract privilege
Clemm, et al. [Page 6]
The modifier "abstract", when applied to a privilege on a resource, The modifier "abstract", when applied to a privilege on a resource,
means the privilege cannot be set in an access control element means the privilege cannot be set in an access control element
(ACE) on that resource . (ACE) on that resource .
access control list (ACL) access control list (ACL)
An "ACL" is a list of access control elements that define access An "ACL" is a list of access control elements that define access
control to a particular resource. control to a particular resource.
access control element (ACE) access control element (ACE)
An "ACE" either grants or denies a particular set of (non-abstract) An "ACE" either grants or denies a particular set of (non-abstract)
privileges for a particular principal. privileges for a particular principal.
inherited ACE inherited ACE
An "inherited ACE" is an ACE that is dynamically shared from the An "inherited ACE" is an ACE that is dynamically shared from the
ACL of another resource. When a shared ACE changes on the primary ACL of another resource. When a shared ACE changes on the primary
resource, it is also changed on inheriting resources. resource, it is also changed on inheriting resources.
protected property protected property
A "protected property" is one whose value cannot be updated except A "protected property" is one whose value cannot be updated except
by a method explicitly defined as updating that specific property. by a method explicitly defined as updating that specific property.
In particular, a protected property cannot be updated with a In particular, a protected property cannot be updated with a
PROPPATCH request. PROPPATCH request.
Clemm, Hopkins, Sedlar, Whitehead [Page 7]
1.2 Notational Conventions 1.2 Notational Conventions
The augmented BNF used by this document to describe protocol The augmented BNF used by this document to describe protocol
elements is described in Section 2.1 of [RFC2616]. Because this elements is described in Section 2.1 of [RFC2616]. Because this
augmented BNF uses the basic production rules provided in Section augmented BNF uses the basic production rules provided in Section
2.2 of [RFC2616], those rules apply to this document as well. 2.2 of [RFC2616], those rules apply to this document as well.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in [RFC2119]. this document are to be interpreted as described in [RFC2119].
skipping to change at line 370 skipping to change at line 376
context of an XML fragment, the string "DAV:" will be prefixed to context of an XML fragment, the string "DAV:" will be prefixed to
the element name. the element name.
2 PRINCIPALS 2 PRINCIPALS
A principal is a network resource that represents a distinct human A principal is a network resource that represents a distinct human
or computational actor that initiates access to network resources. or computational actor that initiates access to network resources.
Users and groups are represented as principals in many Users and groups are represented as principals in many
implementations; other types of principals are also possible. A URI implementations; other types of principals are also possible. A URI
of any scheme MAY be used to identify a principal resource. of any scheme MAY be used to identify a principal resource.
Clemm, et al. [Page 7]
However, servers implementing this specification MUST expose However, servers implementing this specification MUST expose
principal resources at an http(s) URL, which is a privileged scheme principal resources at an http(s) URL, which is a privileged scheme
that points to resources that have additional properties, as that points to resources that have additional properties, as
described in Section 4. So, a principal resource can have multiple described in Section 4. So, a principal resource can have multiple
URIs, one of which has to be an http(s) scheme URL. Although an URIs, one of which has to be an http(s) scheme URL. Although an
implementation SHOULD support PROPFIND and MAY support PROPPATCH to implementation SHOULD support PROPFIND and MAY support PROPPATCH to
access and modify information about a principal, it is not required access and modify information about a principal, it is not required
to do so. to do so.
A principal resource may be a group, where a group is a principal A principal resource may be a group, where a group is a principal
that represents a set of other principals, called the members of that represents a set of other principals, called the members of
the group. If a person or computational agent matches a principal the group. If a person or computational agent matches a principal
resource that is a member of a group, they also match the group. resource that is a member of a group, they also match the group.
Membership in a group is recursive, so if a principal is a member Membership in a group is recursive, so if a principal is a member
of group GRPA, and GRPA is a member of group GRPB, then the of group GRPA, and GRPA is a member of group GRPB, then the
principal is also a member of GRPB. principal is also a member of GRPB.
Clemm, Hopkins, Sedlar, Whitehead [Page 8]
3 PRIVILEGES 3 PRIVILEGES
Ability to perform a given method on a resource SHOULD be Ability to perform a given method on a resource MUST be controlled
controlled by one or more privileges. Authors of protocol by one or more privileges. Authors of protocol extensions that
extensions that define new HTTP methods SHOULD specify which define new HTTP methods SHOULD specify which privileges (by
privileges (by defining new privileges, or mapping to ones below) defining new privileges, or mapping to ones below) are required to
are required to perform the method. A principal with no privileges perform the method. A principal with no privileges to a resource
to a resource SHOULD be denied any HTTP access to that resource, MUST be denied any HTTP access to that resource, unless the
unless the principal matches an ACE constructed using the DAV:all, principal matches an ACE constructed using the DAV:all,
DAV:authenticated, or DAV:unauthenticated pseudo-principals (see DAV:authenticated, or DAV:unauthenticated pseudo-principals (see
Section 5.4.1). Section 5.4.1). Servers MUST report a 403 "Forbidden" error if
access is denied, except in the case where the privilege restricts
the ability to know the resource exists, in which case 404 "Not
Found" may be returned.
Privileges may be containers of other privileges, in which case Privileges may be containers of other privileges, in which case
they are termed "aggregate privileges". If a principal is granted they are termed "aggregate privileges". If a principal is granted
or denied an aggregate privilege, it is semantically equivalent to or denied an aggregate privilege, it is semantically equivalent to
granting or denying each of the aggregated privileges individually. granting or denying each of the aggregated privileges individually.
For example, an implementation may define add-member and remove- For example, an implementation may define add-member and remove-
member privileges that control the ability to add and remove a member privileges that control the ability to add and remove a
member of a group. Since these privileges control the ability to member of a group. Since these privileges control the ability to
update the state of a group, these privileges would be aggregated update the state of a group, these privileges would be aggregated
by the DAV:write privilege on a group, and granting the DAV:write by the DAV:write privilege on a group, and granting the DAV:write
skipping to change at line 421 skipping to change at line 431
Privileges may be declared to be "abstract" for a given resource, Privileges may be declared to be "abstract" for a given resource,
in which case they cannot be set in an ACE on that resource. in which case they cannot be set in an ACE on that resource.
Aggregate and non-aggregate privileges are both capable of being Aggregate and non-aggregate privileges are both capable of being
abstract. Abstract privileges are useful for modeling privileges abstract. Abstract privileges are useful for modeling privileges
that otherwise would not be exposed via the protocol. Abstract that otherwise would not be exposed via the protocol. Abstract
privileges also provide server implementations with flexibility in privileges also provide server implementations with flexibility in
implementing the privileges defined in this specification. For implementing the privileges defined in this specification. For
example, if a server is incapable of separating the read resource example, if a server is incapable of separating the read resource
capability from the read ACL capability, it can still model the capability from the read ACL capability, it can still model the
Clemm, et al. [Page 8]
DAV:read and DAV:read-acl privileges defined in this specification DAV:read and DAV:read-acl privileges defined in this specification
by declaring them abstract, and containing them within a non- by declaring them abstract, and containing them within a non-
abstract aggregate privilege (say, read-all) that holds DAV:read, abstract aggregate privilege (say, read-all) that holds DAV:read,
and DAV:read-acl. In this way, it is possible to set the aggregate and DAV:read-acl. In this way, it is possible to set the aggregate
privilege, read-all, thus coupling the setting of DAV:read and privilege, read-all, thus coupling the setting of DAV:read and
DAV:read-acl, but it is not possible to set DAV:read, or DAV:read- DAV:read-acl, but it is not possible to set DAV:read, or DAV:read-
acl individually. Since aggregate privileges can be abstract, it is acl individually. Since aggregate privileges can be abstract, it is
also possible to use abstract privileges to group or organize non- also possible to use abstract privileges to group or organize non-
abstract privileges. Privilege containment loops are not allowed; abstract privileges. Privilege containment loops are not allowed;
therefore, a privilege MUST NOT contain itself. For example, therefore, a privilege MUST NOT contain itself. For example,
DAV:read cannot contain DAV:read. DAV:read cannot contain DAV:read.
The set of privileges that apply to a particular resource may vary The set of privileges that apply to a particular resource may vary
with the DAV:resourcetype of the resource, as well as between with the DAV:resourcetype of the resource, as well as between
different server implementations. To promote interoperability, different server implementations. To promote interoperability,
however, this specification defines a set of well-known privileges however, this specification defines a set of well-known privileges
Clemm, Hopkins, Sedlar, Whitehead [Page 9]
(e.g. DAV:read, DAV:write, DAV:read-acl, DAV:write-acl, DAV:read- (e.g. DAV:read, DAV:write, DAV:read-acl, DAV:write-acl, DAV:read-
current-user-privilege-set, and DAV:all), which can at least be current-user-privilege-set, and DAV:all), which can at least be
used to classify the other privileges defined on a particular used to classify the other privileges defined on a particular
resource. The access permissions on null resources (defined in resource. The access permissions on null resources (defined in
[RFC2518], Section 3) are solely those they inherit (if any), and [RFC2518], Section 3) are solely those they inherit (if any), and
they are not discoverable (i.e., the access control properties they are not discoverable (i.e., the access control properties
specified in Section 5 are not defined on null resources). On the specified in Section 5 are not defined on null resources). On the
transition from null to stateful resource, the initial access transition from null to stateful resource, the initial access
control list is set by the server's default ACL value policy (if control list is set by the server's default ACL value policy (if
any). any).
skipping to change at line 461 skipping to change at line 471
defined in this specification. Privileges defined by individual defined in this specification. Privileges defined by individual
implementations MUST NOT use the DAV: namespace, and instead should implementations MUST NOT use the DAV: namespace, and instead should
use a namespace that they control, such as an http scheme URL. use a namespace that they control, such as an http scheme URL.
3.1 DAV:read Privilege 3.1 DAV:read Privilege
The read privilege controls methods that return information about The read privilege controls methods that return information about
the state of the resource, including the resource's properties. the state of the resource, including the resource's properties.
Affected methods include GET and PROPFIND. Any implementation- Affected methods include GET and PROPFIND. Any implementation-
defined privilege that also controls access to GET and PROPFIND defined privilege that also controls access to GET and PROPFIND
must be aggregated under DAV:readůif an ACL grants access to must be aggregated under DAV:read—if an ACL grants access to
DAV:read, the client may expect that no other privilege needs to be DAV:read, the client may expect that no other privilege needs to be
granted to have access to GET and PROPFIND. Additionally, the read granted to have access to GET and PROPFIND. Additionally, the read
privilege MAY control the OPTIONS method. privilege MUST control the OPTIONS method.
<!ELEMENT read EMPTY> <!ELEMENT read EMPTY>
3.2 DAV:write Privilege 3.2 DAV:write Privilege
The write privilege controls methods that lock a resource or modify The write privilege controls methods that lock a resource or modify
the content, dead properties, or (in the case of a collection) the content, dead properties, or (in the case of a collection)
membership of the resource, such as PUT and PROPPATCH. Note that membership of the resource, such as PUT and PROPPATCH. Note that
state modification is also controlled via locking (see section 5.3 state modification is also controlled via locking (see section 5.3
of [WEBDAV]), so effective write access requires that both write of [WEBDAV]), so effective write access requires that both write
privileges and write locking requirements are satisfied. Any privileges and write locking requirements are satisfied. Any
Clemm, et al. [Page 9]
implementation-defined privilege that also controls access to implementation-defined privilege that also controls access to
methods modifying content, dead properties or collection membership methods modifying content, dead properties or collection membership
must be aggregated under DAV:write, e.g. if an ACL grants access to must be aggregated under DAV:write, e.g. if an ACL grants access to
DAV:write, the client may expect that no other privilege needs to DAV:write, the client may expect that no other privilege needs to
be granted to have access to PUT and PROPPATCH. be granted to have access to PUT and PROPPATCH.
<!ELEMENT write EMPTY> <!ELEMENT write EMPTY>
3.3 DAV:write-properties 3.3 DAV:write-properties
The DAV:write-properties privilege controls methods that modify the The DAV:write-properties privilege controls methods that modify the
dead properties of the resource, such as PROPPATCH. Whether this dead properties of the resource, such as PROPPATCH. Whether this
Clemm, Hopkins, Sedlar, Whitehead [Page 10]
privilege may be used to control access to any live properties is privilege may be used to control access to any live properties is
determined by the implementation. Any implementation-defined determined by the implementation. Any implementation-defined
privilege that also controls access to methods modifying dead privilege that also controls access to methods modifying dead
properties must be aggregated under DAV:write-propertiesůe.g. if an properties must be aggregated under DAV:write-properties—e.g. if an
ACL grants access to DAV:write-properties, the client can safely ACL grants access to DAV:write-properties, the client can safely
expect that no other privilege needs to be granted to have access expect that no other privilege needs to be granted to have access
to PROPPATCH. to PROPPATCH.
<!ELEMENT write-properties EMPTY> <!ELEMENT write-properties EMPTY>
3.4 DAV:write-content 3.4 DAV:write-content
The DAV:write-content privilege controls methods that modify the The DAV:write-content privilege controls methods that modify the
content or (in the case of a collection) membership of the content or (in the case of a collection) membership of the
resource, such as PUT and DELETE. Any implementation-defined resource, such as PUT and DELETE. Any implementation-defined
privilege that also controls access to content or alteration of privilege that also controls access to content or alteration of
collection membership must be aggregated under DAV:write-contentů collection membership must be aggregated under DAV:write-content—
e.g. if an ACL grants access to DAV:write-content, the client can e.g. if an ACL grants access to DAV:write-content, the client can
safely expect that no other privilege needs to be granted to have safely expect that no other privilege needs to be granted to have
access to PUT or DELETE. access to PUT or DELETE.
<!ELEMENT write-content EMPTY> <!ELEMENT write-content EMPTY>
3.5 DAV:unlock 3.5 DAV:unlock
The DAV:unlock privilege controls the use of the UNLOCK method by a The DAV:unlock privilege controls the use of the UNLOCK method by a
principal other than the lock owner (the principal that created a principal other than the lock owner (the principal that created a
skipping to change at line 532 skipping to change at line 542
under DAV:unlock. under DAV:unlock.
A lock owner can always remove a lock by issuing an UNLOCK with the A lock owner can always remove a lock by issuing an UNLOCK with the
correct lock token and authentication credentials. That is, even if correct lock token and authentication credentials. That is, even if
a principal does not have DAV:unlock privilege, they can still a principal does not have DAV:unlock privilege, they can still
remove locks they own. Principals other than the lock owner can remove locks they own. Principals other than the lock owner can
remove a lock only if they have DAV:unlock privilege and they issue remove a lock only if they have DAV:unlock privilege and they issue
an UNLOCK with the correct lock token. Lock timeout is not affected an UNLOCK with the correct lock token. Lock timeout is not affected
by the DAV:unlock privilege. by the DAV:unlock privilege.
Clemm, et al. [Page 10]
<!ELEMENT unlock EMPTY> <!ELEMENT unlock EMPTY>
Clemm, Hopkins, Sedlar, Whitehead [Page 11]
3.6 DAV:read-acl Privilege 3.6 DAV:read-acl Privilege
The DAV:read-acl privilege controls the use of PROPFIND to retrieve The DAV:read-acl privilege controls the use of PROPFIND to retrieve
the DAV:acl property of the resource. the DAV:acl property of the resource.
<!ELEMENT read-acl EMPTY> <!ELEMENT read-acl EMPTY>
3.7 DAV:read-current-user-privilege-set Privilege 3.7 DAV:read-current-user-privilege-set Privilege
The DAV:read-current-user-privilege-set privilege controls the use The DAV:read-current-user-privilege-set privilege controls the use
skipping to change at line 570 skipping to change at line 580
<!ELEMENT read-current-user-privilege-set EMPTY> <!ELEMENT read-current-user-privilege-set EMPTY>
3.8 DAV:write-acl Privilege 3.8 DAV:write-acl Privilege
The DAV:write-acl privilege controls use of the ACL method to The DAV:write-acl privilege controls use of the ACL method to
modify the DAV:acl property of the resource. modify the DAV:acl property of the resource.
<!ELEMENT write-acl EMPTY> <!ELEMENT write-acl EMPTY>
3.9 DAV:all Privilege 3.9 DAV:delete Privilege
The DAV:delete privilege controls use of the DELETE method on the
specified resource. You must also have DAV:write-content on the
collection containing the resource for the DELETE to succeed.
<!ELEMENT delete EMPTY>
3.10DAV:all Privilege
DAV:all is an aggregate privilege that contains the entire set of DAV:all is an aggregate privilege that contains the entire set of
privileges that can be applied to the resource. privileges that can be applied to the resource.
<!ELEMENT all EMPTY> <!ELEMENT all EMPTY>
3.10 Aggregation of Predefined Privileges Clemm, et al. [Page 11]
3.11Aggregation of Predefined Privileges
Server implementations are free to aggregate the predefined Server implementations are free to aggregate the predefined
privileges (defined above in Sections 3.1-3.9) subject to the privileges (defined above in Sections 3.1-3.9) subject to the
following limitations: following limitations:
Clemm, Hopkins, Sedlar, Whitehead [Page 12]
DAV:read-acl MUST NOT contain DAV:read, DAV:write, DAV:write-acl, DAV:read-acl MUST NOT contain DAV:read, DAV:write, DAV:write-acl,
DAV:write-properties, DAV:write-content, or DAV:read-current-user- DAV:write-properties, DAV:write-content, or DAV:read-current-user-
privilege-set. privilege-set.
DAV:write-acl MUST NOT contain DAV:write, DAV:read, DAV:read-acl, DAV:write-acl MUST NOT contain DAV:write, DAV:read, DAV:read-acl,
or DAV:read-current-user-privilege-set. or DAV:read-current-user-privilege-set.
DAV:read-current-user-privilege-set MUST NOT contain DAV:write, DAV:read-current-user-privilege-set MUST NOT contain DAV:write,
DAV:read, DAV:read-acl, or DAV:write-acl. DAV:read, DAV:read-acl, or DAV:write-acl.
skipping to change at line 620 skipping to change at line 638
property. The element type declaration for DAV:principal is: property. The element type declaration for DAV:principal is:
<!ELEMENT principal EMPTY> <!ELEMENT principal EMPTY>
This protocol defines the following additional properties for a This protocol defines the following additional properties for a
principal. Since it can be expensive for a server to retrieve principal. Since it can be expensive for a server to retrieve
access control information, the name and value of these properties access control information, the name and value of these properties
SHOULD NOT be returned by a PROPFIND allprop request (as defined in SHOULD NOT be returned by a PROPFIND allprop request (as defined in
Section 12.14.1 of [RFC2518]). Section 12.14.1 of [RFC2518]).
Clemm, Hopkins, Sedlar, Whitehead [Page 13]
4.1 DAV:alternate-URI-set 4.1 DAV:alternate-URI-set
This protected property, if non-empty, contains the URIs of network This protected property, if non-empty, contains the URIs of network
resources with additional descriptive information about the resources with additional descriptive information about the
principal. This property identifies additional network resources principal. This property identifies additional network resources
(i.e., it contains one or more URIs) that may be consulted by a (i.e., it contains one or more URIs) that may be consulted by a
client to gain additional knowledge concerning a principal. One client to gain additional knowledge concerning a principal. One
expected use for this property is the storage of an LDAP [RFC2255] expected use for this property is the storage of an LDAP [RFC2255]
scheme URL. A user-agent encountering an LDAP URL could use LDAP scheme URL. A user-agent encountering an LDAP URL could use LDAP
[RFC2589] to retrieve additional machine-readable directory [RFC2589] to retrieve additional machine-readable directory
Clemm, et al. [Page 12]
information about the principal, and display that information in information about the principal, and display that information in
its user interface. Support for this property is REQUIRED, and the its user interface. Support for this property is REQUIRED, and the
value is empty if no alternate URI exists for the principal. value is empty if no alternate URI exists for the principal.
<!ELEMENT alternate-URI-set (href*)> <!ELEMENT alternate-URI-set (href*)>
4.2 DAV:principal-URL 4.2 DAV:principal-URL
A principal may have many URLs, but there must be one primary URL A principal may have many URLs, but there must be one "principal
that clients can use to uniquely identify a principalůthe URL" that clients can use to uniquely identify a principal. This
principal-URL. This protected property contains the URL that MUST protected property contains the URL that MUST be used to identify
be used to identify this principal in an ACL request. Support for this principal in an ACL request. Support for this property is
this property is REQUIRED. REQUIRED.
<!ELEMENT principal-URL (href)> <!ELEMENT principal-URL (href)>
4.3 DAV:group-member-set 4.3 DAV:group-member-set
This property of a group principal identifies the principals that This property of a group principal identifies the principals that
are direct members of this group. Since a group may be a member of are direct members of this group. Since a group may be a member of
another group, a group may also have indirect members (i.e. the another group, a group may also have indirect members (i.e. the
members of its direct members). A URL in the DAV:group-member-set members of its direct members). A URL in the DAV:group-member-set
for a principal MUST be the DAV:principal-URL of that principal. for a principal MUST be the DAV:principal-URL of that principal.
skipping to change at line 668 skipping to change at line 687
This protected property identifies the groups in which the This protected property identifies the groups in which the
principal is directly a member. Note that a server may allow a principal is directly a member. Note that a server may allow a
group to be a member of another group, in which case the DAV:group- group to be a member of another group, in which case the DAV:group-
membership of those other groups would need to be queried in order membership of those other groups would need to be queried in order
to determine the groups in which the principal is indirectly a to determine the groups in which the principal is indirectly a
member. Support for this property is REQUIRED. member. Support for this property is REQUIRED.
<!ELEMENT group-membership (href*)> <!ELEMENT group-membership (href*)>
Clemm, Hopkins, Sedlar, Whitehead [Page 14]
5 ACCESS CONTROL PROPERTIES 5 ACCESS CONTROL PROPERTIES
This specification defines a number of new properties for WebDAV This specification defines a number of new properties for WebDAV
resources. Access control properties may be retrieved just like resources. Access control properties may be retrieved just like
other WebDAV properties, using the PROPFIND method. Since it is other WebDAV properties, using the PROPFIND method. Since it is
expensive, for many servers, to retrieve access control expensive, for many servers, to retrieve access control
information, a PROPFIND allprop request (as defined in Section information, a PROPFIND allprop request (as defined in Section
12.14.1 of [RFC2518]) SHOULD NOT return the names and values of the 12.14.1 of [RFC2518]) SHOULD NOT return the names and values of the
properties defined in this section. properties defined in this section.
Access control properties (especially DAV:acl and DAV:inherited-
acl-set) are defined on the resource identified by the Request-URI
of a PROPFIND request. A direct consequence is that if the resource
is accessible via multiple URI, the value of access control
properties is the same across these URI.
Clemm, et al. [Page 13]
HTTP resources that support the WebDAV Access Control Protocol MUST HTTP resources that support the WebDAV Access Control Protocol MUST
contain the following properties. Null resources (described in contain the following properties. Null resources (described in
Section 3 of [RFC2518]) MUST NOT contain the following properties: Section 3 of [RFC2518]) MUST NOT contain the following properties.
5.1 DAV:owner 5.1 DAV:owner
This protected property identifies a particular principal as being This protected property identifies a particular principal as being
the "owner" of the resource. Since the owner of a resource often the "owner" of the resource. Since the owner of a resource often
has special access control capabilities (e.g., the owner frequently has special access control capabilities (e.g., the owner frequently
has permanent DAV:write-acl privilege), clients might display the has permanent DAV:write-acl privilege), clients might display the
resource owner in their user interface. resource owner in their user interface.
<!ELEMENT owner (href)> <!ELEMENT owner (href)>
5.1.1 Example: Retrieving DAV:owner 5.1.1 Example: Retrieving DAV:owner
This example shows a client request for the value of the DAV:owner This example shows a client request for the value of the DAV:owner
property from a collection resource with URL property from a collection resource with URL
http://www.webdav.org/papers/. The principal making the request is http://www.example.com/papers/. The principal making the request is
authenticated using Digest authentication. The value of DAV:owner authenticated using Digest authentication. The value of DAV:owner
is the URL http://www.webdav.org/acl/users/gstein, wrapped in the is the URL http://www.example.com/acl/users/gstein, wrapped in the
DAV:href XML element. DAV:href XML element.
>> Request << >> Request <<
PROPFIND /papers/ HTTP/1.1 PROPFIND /papers/ HTTP/1.1
Host: www.webdav.org Host: www.example.com
Content-type: text/xml; charset="utf-8" Content-type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
Depth: 0 Depth: 0
Authorization: Digest username="jim", Authorization: Digest username="jim",
realm="jim@webdav.org", nonce="...", realm="jim@webdav.org", nonce="...",
uri="/papers/", response="...", opaque="..." uri="/papers/", response="...", opaque="..."
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:propfind xmlns:D="DAV:"> <D:propfind xmlns:D="DAV:">
<D:prop> <D:prop>
<D:owner/> <D:owner/>
</D:prop> </D:prop>
</D:propfind> </D:propfind>
Clemm, Hopkins, Sedlar, Whitehead [Page 15]
>> Response << >> Response <<
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:multistatus xmlns:D="DAV:"> <D:multistatus xmlns:D="DAV:">
<D:response> <D:response>
<D:href>http://www.webdav.org/papers/</D:href> <D:href>http://www.example.com/papers/</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
Clemm, et al. [Page 14]
<D:owner> <D:owner>
<D:href>http://www.webdav.org/acl/users/gstein</D:href> <D:href>http://www.example.com/acl/users/gstein</D:href>
</D:owner> </D:owner>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
</D:multistatus> </D:multistatus>
5.1.2 Example: An Attempt to Set DAV:owner 5.1.2 Example: An Attempt to Set DAV:owner
The following example shows a client request to modify the value of The following example shows a client request to modify the value of
the DAV:owner property on the resource with URL the DAV:owner property on the resource with URL
<http://www.webdav.org/papers>. Since DAV:owner is a protected <http://www.example.com/papers>. Since DAV:owner is a protected
property, the server responds with a 207 (Multi-Status) response property, the server responds with a 207 (Multi-Status) response
that contains a 403 (Forbidden) status code for the act of setting that contains a 403 (Forbidden) status code for the act of setting
DAV:owner. Section 8.2.1 of [RFC2518] describes PROPPATCH status DAV:owner. Section 8.2.1 of [RFC2518] describes PROPPATCH status
code information, and Section 11 of [RFC2518] describes the Multi- code information, and Section 11 of [RFC2518] describes the Multi-
Status response. Status response.
>> Request << >> Request <<
PROPPATCH /papers/ HTTP/1.1 PROPPATCH /papers/ HTTP/1.1
Host: www.webdav.org Host: www.example.com
Content-type: text/xml; charset="utf-8" Content-type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
Depth: 0 Depth: 0
Authorization: Digest username="jim", Authorization: Digest username="jim",
realm="jim@webdav.org", nonce="...", realm="jim@webdav.org", nonce="...",
uri="/papers/", response="...", opaque="..." uri="/papers/", response="...", opaque="..."
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:propertyupdate xmlns:D="DAV:"> <D:propertyupdate xmlns:D="DAV:">
<D:set> <D:set>
Clemm, Hopkins, Sedlar, Whitehead [Page 16]
<D:prop> <D:prop>
<D:owner> <D:owner>
<D:href>http://www.webdav.org/acl/users/jim</D:href> <D:href>http://www.example.com/acl/users/jim</D:href>
</D:owner> </D:owner>
</D:prop> </D:prop>
</D:set> </D:set>
</D:propertyupdate> </D:propertyupdate>
>> Response << >> Response <<
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:multistatus xmlns:D="DAV:"> <D:multistatus xmlns:D="DAV:">
<D:response> <D:response>
<D:href>http://www.webdav.org/papers/</D:href> <D:href>http://www.example.com/papers/</D:href>
<D:propstat> <D:propstat>
Clemm, et al. [Page 15]
<D:prop><D:owner/></D:prop> <D:prop><D:owner/></D:prop>
<D:status>HTTP/1.1 403 Forbidden</D:status> <D:status>HTTP/1.1 403 Forbidden</D:status>
<D:responsedescription> <D:responsedescription>
Failure to set protected property (DAV:owner) Failure to set protected property (DAV:owner)
</D:responsedescription> </D:responsedescription>
</D:propstat> </D:propstat>
</D:response> </D:response>
</D:multistatus> </D:multistatus>
5.2 DAV:supported-privilege-set 5.2 DAV:supported-privilege-set
skipping to change at line 817 skipping to change at line 843
<!ELEMENT supported-privilege <!ELEMENT supported-privilege
(privilege, abstract?, description, supported-privilege*)> (privilege, abstract?, description, supported-privilege*)>
<!ELEMENT privilege ANY> <!ELEMENT privilege ANY>
An abstract privilege MUST NOT be used in an ACE for that resource. An abstract privilege MUST NOT be used in an ACE for that resource.
Servers MUST fail an attempt to set an abstract privilege. Servers MUST fail an attempt to set an abstract privilege.
<!ELEMENT abstract EMPTY> <!ELEMENT abstract EMPTY>
Clemm, Hopkins, Sedlar, Whitehead [Page 17]
A description is a human-readable description of what this A description is a human-readable description of what this
privilege controls access to. Servers MUST indicate the human privilege controls access to. Servers MUST indicate the human
language of the description using the xml:lang attribute and SHOULD language of the description using the xml:lang attribute and SHOULD
consider the HTTP Accept-Language request header when selecting one consider the HTTP Accept-Language request header when selecting one
of multiple available languages. of multiple available languages.
<!ELEMENT description #PCDATA> <!ELEMENT description #PCDATA>
It is envisioned that a WebDAV ACL-aware administrative client It is envisioned that a WebDAV ACL-aware administrative client
would list the supported privileges in a dialog box, and allow the would list the supported privileges in a dialog box, and allow the
user to choose non-abstract privileges to apply in an ACE. The user to choose non-abstract privileges to apply in an ACE. The
privileges tree is useful programmatically to map well-known privileges tree is useful programmatically to map well-known
privileges (defined by WebDAV or other standards groups) into privileges (defined by WebDAV or other standards groups) into
privileges that are supported by any particular server privileges that are supported by any particular server
implementation. The privilege tree also serves to hide complexity implementation. The privilege tree also serves to hide complexity
in implementations allowing large number of privileges to be in implementations allowing large number of privileges to be
defined by displaying aggregates to the user. defined by displaying aggregates to the user.
5.2.1 Example: Retrieving a List of Privileges Supported on a 5.2.1Example: Retrieving a List of Privileges Supported on a Resource
Resource
This example shows a client request for the DAV:supported- This example shows a client request for the DAV:supported-
privilege-set property on the resource privilege-set property on the resource
http://www.webdav.org/papers/. The value of the DAV:supported-
Clemm, et al. [Page 16]
http://www.example.com/papers/. The value of the DAV:supported-
privilege-set property is a tree of supported privileges (using privilege-set property is a tree of supported privileges (using
"[XML Namespace , localname]" to identify each privilege): "[XML Namespace , localname]" to identify each privilege):
[DAV:, all] (aggregate, abstract) [DAV:, all] (aggregate, abstract)
| |
+-- [DAV:, read] (aggregate) +-- [DAV:, read] (aggregate)
| |
+-- [DAV:, read-acl] (abstract) +-- [DAV:, read-acl] (abstract)
+-- [DAV:, read-current-user-privilege-set] (abstract) +-- [DAV:, read-current-user-privilege-set] (abstract)
| |
+-- [DAV:, write] (aggregate) +-- [DAV:, write] (aggregate)
| |
+-- [DAV:, write-acl] (abstract) +-- [DAV:, write-acl] (abstract)
+-- [DAV:, write-properties] +-- [DAV:, write-properties]
+-- [DAV:, write-content] +-- [DAV:, write-content]
| |
+-- [DAV:, unlock] +-- [DAV:, unlock]
This privilege tree is not normative (except that it reflects the This privilege tree is not normative (except that it reflects the
normative aggregation rules given in Section 3.10), and many normative aggregation rules given in Section 3.11), and many
possible privilege trees are possible. possible privilege trees are possible.
Clemm, Hopkins, Sedlar, Whitehead [Page 18]
>> Request << >> Request <<
PROPFIND /papers/ HTTP/1.1 PROPFIND /papers/ HTTP/1.1
Host: www.webdav.org Host: www.example.com
Content-type: text/xml; charset="utf-8" Content-type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
Depth: 0 Depth: 0
Authorization: Digest username="gclemm", Authorization: Digest username="gclemm",
realm="gclemm@webdav.org", nonce="...", realm="gclemm@webdav.org", nonce="...",
uri="/papers/", response="...", opaque="..." uri="/papers/", response="...", opaque="..."
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:propfind xmlns:D="DAV:"> <D:propfind xmlns:D="DAV:">
<D:prop> <D:prop>
skipping to change at line 892 skipping to change at line 917
>> Response << >> Response <<
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:multistatus xmlns:D="DAV:"> <D:multistatus xmlns:D="DAV:">
<D:response> <D:response>
<D:href>http://www.webdav.org/papers/</D:href> <D:href>http://www.example.com/papers/</D:href>
Clemm, et al. [Page 17]
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<D:supported-privilege-set> <D:supported-privilege-set>
<D:supported-privilege> <D:supported-privilege>
<D:privilege> <D:all/> </D:privilege> <D:privilege> <D:all/> </D:privilege>
<D:abstract/> <D:abstract/>
<D:description xml:lang="en">Any <D:description xml:lang="en">Any operation</D:description>
operation</D:description>
<D:supported-privilege> <D:supported-privilege>
<D:privilege> <D:read/> </D:privilege> <D:privilege> <D:read/> </D:privilege>
<D:description xml:lang="en">Read any <D:description xml:lang="en">Read any object</D:description>
object</D:description>
<D:supported-privilege> <D:supported-privilege>
<D:privilege> <D:read-acl/> </D:privilege> <D:privilege> <D:read-acl/> </D:privilege>
<D:abstract/> <D:abstract/>
<D:description xml:lang="en">Read <D:description xml:lang="en">Read ACL</D:description>
ACL</D:description>
</D:supported-privilege> </D:supported-privilege>
<D:supported-privilege> <D:supported-privilege>
<D:privilege> <D:privilege>
Clemm, Hopkins, Sedlar, Whitehead [Page 19]
<D:read-current-user-privilege-set/> <D:read-current-user-privilege-set/>
</D:privilege> </D:privilege>
<D:abstract/> <D:abstract/>
<D:description xml:lang="en">Read current user <D:description xml:lang="en">Read current user privilege
privilege set property</D:description> set property</D:description>
</D:supported-privilege> </D:supported-privilege>
</D:supported-privilege> </D:supported-privilege>
<D:supported-privilege> <D:supported-privilege>
<D:privilege> <D:write/> </D:privilege> <D:privilege> <D:write/> </D:privilege>
<D:description xml:lang="en">Write any <D:description xml:lang="en">Write any object</D:description>
object</D:description>
<D:supported-privilege> <D:supported-privilege>
<D:privilege> <D:write-acl/> </D:privilege> <D:privilege> <D:write-acl/> </D:privilege>
<D:description xml:lang="en">Write <D:description xml:lang="en">Write ACL</D:description>
ACL</D:description>
<D:abstract/> <D:abstract/>
</D:supported-privilege> </D:supported-privilege>
<D:supported-privilege> <D:supported-privilege>
<D:privilege> <D:write-properties/> </D:privilege> <D:privilege> <D:write-properties/> </D:privilege>
<D:description xml:lang="en">Write <D:description xml:lang="en">Write
properties</D:description> properties</D:description>
</D:supported-privilege> </D:supported-privilege>
<D:supported-privilege> <D:supported-privilege>
<D:privilege> <D:write-content/> </D:privilege> <D:privilege> <D:write-content/> </D:privilege>
<D:description xml:lang="en">Write resource <D:description xml:lang="en">Write resource
skipping to change at line 954 skipping to change at line 974
<D:privilege> <D:unlock/> </D:privilege> <D:privilege> <D:unlock/> </D:privilege>
<D:description xml:lang="en">Unlock <D:description xml:lang="en">Unlock
resource</D:description> resource</D:description>
</D:supported-privilege> </D:supported-privilege>
</D:supported-privilege> </D:supported-privilege>
</D:supported-privilege-set> </D:supported-privilege-set>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
Clemm, et al. [Page 18]
</D:multistatus> </D:multistatus>
5.3 DAV:current-user-privilege-set 5.3 DAV:current-user-privilege-set
DAV:current-user-privilege-set is a protected property containing DAV:current-user-privilege-set is a protected property containing
the exact set of privileges (as computed by the server) granted to the exact set of privileges (as computed by the server) granted to
the currently authenticated HTTP user. Aggregate privileges and the currently authenticated HTTP user. Aggregate privileges and
their contained privileges are listed. A user-agent can use the their contained privileges are listed. A user-agent can use the
value of this property to adjust its user interface to make actions value of this property to adjust its user interface to make actions
Clemm, Hopkins, Sedlar, Whitehead [Page 20]
inaccessible (e.g., by graying out a menu item or button) for which inaccessible (e.g., by graying out a menu item or button) for which
the current principal does not have permission. This is the current principal does not have permission. This property is
particularly useful for an access control user interface, which can also useful for determining what operations the current principal
be constructed without knowing the ACE combining semantics of the can perform, without having to actually execute an operation.
server. This property is also useful for determining what
operations the current principal can perform, without having to
actually execute an operation.
<!ELEMENT current-user-privilege-set (privilege*)> <!ELEMENT current-user-privilege-set (privilege*)>
<!ELEMENT privilege ANY> <!ELEMENT privilege ANY>
If the current user is granted a specific privilege, that privilege If the current user is granted a specific privilege, that privilege
must belong to the set of privileges that may be set on this must belong to the set of privileges that may be set on this
resource. Therefore, each element in the DAV:current-user- resource. Therefore, each element in the DAV:current-user-
privilege-set property MUST identify a non-abstract privilege from privilege-set property MUST identify a non-abstract privilege from
the DAV:supported-privilege-set property. the DAV:supported-privilege-set property.
5.3.1 Example: Retrieving the User's Current Set of Assigned 5.3.1Example: Retrieving the User's Current Set of Assigned Privileges
Privileges
Continuing the example from Section 5.2.1, this example shows a Continuing the example from Section 5.2.1, this example shows a
client requesting the DAV:current-user-privilege-set property from client requesting the DAV:current-user-privilege-set property from
the resource with URL http://www.webdav.org/papers/. The username the resource with URL http://www.example.com/papers/. The username
of the principal making the request is "khare", and Digest of the principal making the request is "khare", and Digest
authentication is used in the request. The principal with username authentication is used in the request. The principal with username
"khare" has been granted the DAV:read privilege. Since the DAV:read "khare" has been granted the DAV:read privilege. Since the DAV:read
privilege contains the DAV:read-acl and DAV:read-current-user- privilege contains the DAV:read-acl and DAV:read-current-user-
privilege-set privileges (see Section 5.2.1), the principal with privilege-set privileges (see Section 5.2.1), the principal with
username "khare" can read the ACL property, and the DAV:current- username "khare" can read the ACL property, and the DAV:current-
user-privilege-set property. However, the DAV:all, DAV:read-acl, user-privilege-set property. However, the DAV:all, DAV:read-acl,
DAV:write-acl and DAV:read-current-user-privilege-set privileges DAV:write-acl and DAV:read-current-user-privilege-set privileges
are not listed in the value of DAV:current-user-privilege-set, are not listed in the value of DAV:current-user-privilege-set,
since (for this example) they are abstract privileges. DAV:write is since (for this example) they are abstract privileges. DAV:write is
not listed since the principal with username "khare" is not listed not listed since the principal with username "khare" is not listed
in an ACE granting that principal write permission. in an ACE granting that principal write permission.
>> Request << >> Request <<
PROPFIND /papers/ HTTP/1.1 PROPFIND /papers/ HTTP/1.1
Host: www.webdav.org Host: www.example.com
Content-type: text/xml; charset="utf-8" Content-type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
Depth: 0 Depth: 0
Authorization: Digest username="khare", Authorization: Digest username="khare",
realm="khare@webdav.org", nonce="...", realm="khare@webdav.org", nonce="...",
uri="/papers/", response="...", opaque="..." uri="/papers/", response="...", opaque="..."
Clemm, Hopkins, Sedlar, Whitehead [Page 21]
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
Clemm, et al. [Page 19]
<D:propfind xmlns:D="DAV:"> <D:propfind xmlns:D="DAV:">
<D:prop> <D:prop>
<D:current-user-privilege-set/> <D:current-user-privilege-set/>
</D:prop> </D:prop>
</D:propfind> </D:propfind>
>> Response << >> Response <<
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:multistatus xmlns:D="DAV:"> <D:multistatus xmlns:D="DAV:">
<D:response> <D:response>
<D:href>http://www.webdav.org/papers/</D:href> <D:href>http://www.example.com/papers/</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<D:current-user-privilege-set> <D:current-user-privilege-set>
<D:privilege> <D:read/> </D:privilege> <D:privilege> <D:read/> </D:privilege>
</D:current-user-privilege-set> </D:current-user-privilege-set>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
</D:multistatus> </D:multistatus>
skipping to change at line 1053 skipping to change at line 1070
This is a protected property that specifies the list of access This is a protected property that specifies the list of access
control entries (ACEs), which define what principals are to get control entries (ACEs), which define what principals are to get
what privileges for this resource. what privileges for this resource.
<!ELEMENT acl (ace*) > <!ELEMENT acl (ace*) >
Each DAV:ace element specifies the set of privileges to be either Each DAV:ace element specifies the set of privileges to be either
granted or denied to a single principal. If the DAV:acl property granted or denied to a single principal. If the DAV:acl property
is empty, no principal is granted any privilege. is empty, no principal is granted any privilege.
<!ELEMENT ace (invert | principal, (grant|deny), protected?, <!ELEMENT ace (invert | principal, (grant|deny), protected?, inherited?)>
inherited?)>
5.4.1 ACE Principal 5.4.1 ACE Principal
The DAV:principal element identifies the principal to which this The DAV:principal element identifies the principal to which this
ACE applies. ACE applies.
Clemm, Hopkins, Sedlar, Whitehead [Page 22]
<!ELEMENT principal ((href) <!ELEMENT principal ((href)
| all | authenticated | unauthenticated | all | authenticated | unauthenticated
| property | self)> | property | self)>
The current user matches DAV:href only if that user is The current user matches DAV:href only if that user is
authenticated as being (or being a member of) the principal authenticated as being (or being a member of) the principal
identified by the URL contained by that DAV:href. identified by the URL contained by that DAV:href.
Clemm, et al. [Page 20]
The current user always matches DAV:all. The current user always matches DAV:all.
<!ELEMENT all EMPTY> <!ELEMENT all EMPTY>
The current user matches DAV:authenticated only if authenticated. The current user matches DAV:authenticated only if authenticated.
<!ELEMENT authenticated EMPTY> <!ELEMENT authenticated EMPTY>
The current user matches DAV:unauthenticated only if not The current user matches DAV:unauthenticated only if not
authenticated. authenticated.
skipping to change at line 1107 skipping to change at line 1123
<!ELEMENT property ANY> <!ELEMENT property ANY>
Alternately, some servers may support ACEs applying to those users Alternately, some servers may support ACEs applying to those users
NOT matching the current principal, e.g. all users not in a NOT matching the current principal, e.g. all users not in a
particular group. This can be done by wrapping the DAV:principal particular group. This can be done by wrapping the DAV:principal
element with DAV:invert. element with DAV:invert.
<!ELEMENT invert principal> <!ELEMENT invert principal>
Clemm, Hopkins, Sedlar, Whitehead [Page 23]
The current user matches DAV:self in a DAV:acl property of the The current user matches DAV:self in a DAV:acl property of the
resource only if that resource is a principal and that principal resource only if that resource is a principal and that principal
matches the current user or, if the principal is a group, a member matches the current user or, if the principal is a group, a member
of that group matches the current user. of that group matches the current user.
<!ELEMENT self EMPTY> <!ELEMENT self EMPTY>
5.4.2 ACE Grant and Deny 5.4.2 ACE Grant and Deny
Each DAV:grant or DAV:deny element specifies the set of privileges Each DAV:grant or DAV:deny element specifies the set of privileges
to be either granted or denied to the specified principal. A to be either granted or denied to the specified principal. A
DAV:grant or DAV:deny element of the DAV:acl of a resource MUST DAV:grant or DAV:deny element of the DAV:acl of a resource MUST
only contain non-abstract elements specified in the DAV:supported- only contain non-abstract elements specified in the DAV:supported-
privilege-set of that resource. privilege-set of that resource.
<!ELEMENT grant (privilege+)> <!ELEMENT grant (privilege+)>
Clemm, et al. [Page 21]
<!ELEMENT deny (privilege+)> <!ELEMENT deny (privilege+)>
<!ELEMENT privilege ANY> <!ELEMENT privilege ANY>
5.4.3 ACE Protection 5.4.3 ACE Protection
A server indicates an ACE is protected by including the A server indicates an ACE is protected by including the
DAV:protected element in the ACE. If the ACL of a resource contains DAV:protected element in the ACE. If the ACL of a resource contains
an ACE with a DAV:protected element, an attempt to remove that ACE an ACE with a DAV:protected element, an attempt to remove that ACE
from the ACL MUST fail. from the ACL MUST fail.
skipping to change at line 1154 skipping to change at line 1171
Note that ACE inheritance is not the same as ACL initialization. Note that ACE inheritance is not the same as ACL initialization.
ACL initialization defines the ACL that a newly created resource ACL initialization defines the ACL that a newly created resource
will use (if not specified). ACE inheritance refers to an ACE that will use (if not specified). ACE inheritance refers to an ACE that
is logically shared - where an update to the resource containing an is logically shared - where an update to the resource containing an
ACE will affect the ACE of each resource that inherits that ACE. ACE will affect the ACE of each resource that inherits that ACE.
The method by which ACLs are initialized or by which ACEs are The method by which ACLs are initialized or by which ACEs are
inherited is not defined by this document. inherited is not defined by this document.
<!ELEMENT inherited (href)> <!ELEMENT inherited (href)>
Clemm, Hopkins, Sedlar, Whitehead [Page 24]
5.4.5 Example: Retrieving a Resource's Access Control List 5.4.5 Example: Retrieving a Resource's Access Control List
Continuing the example from Sections 5.2.1 and 5.3.1, this example Continuing the example from Sections 5.2.1 and 5.3.1, this example
shows a client requesting the DAV:acl property from the resource shows a client requesting the DAV:acl property from the resource
with URL http://www.webdav.org/papers/. There are two ACEs defined with URL http://www.example.com/papers/. There are two ACEs defined
in this ACL: in this ACL:
ACE #1: The group identified by URL ACE #1: The group identified by URL
http://www.webdav.org/acl/groups/maintainers (the group of site http://www.example.com/acl/groups/maintainers (the group of site
maintainers) is granted DAV:write privilege. Since (for this maintainers) is granted DAV:write privilege. Since (for this
example) DAV:write contains the DAV:write-acl privilege (see example) DAV:write contains the DAV:write-acl privilege (see
Section 5.2.1), this means the "maintainers" group can also modify Section 5.2.1), this means the "maintainers" group can also modify
the access control list. the access control list.
ACE #2: All principals (DAV:all) are granted the DAV:read ACE #2: All principals (DAV:all) are granted the DAV:read
privilege. Since (for this example) DAV:read contains DAV:read-acl privilege. Since (for this example) DAV:read contains DAV:read-acl
and DAV:read-current-user-privilege-set, this means all users and DAV:read-current-user-privilege-set, this means all users
(including all members of the "maintainers" group) can read the (including all members of the "maintainers" group) can read the
DAV:acl property and the DAV:current-user-privilege-set property. DAV:acl property and the DAV:current-user-privilege-set property.
>> Request << >> Request <<
PROPFIND /papers/ HTTP/1.1 PROPFIND /papers/ HTTP/1.1
Host: www.webdav.org
Clemm, et al. [Page 22]
Host: www.example.com
Content-type: text/xml; charset="utf-8" Content-type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
Depth: 0 Depth: 0
Authorization: Digest username="masinter", Authorization: Digest username="masinter",
realm="webdav.org", nonce="...", realm="webdav.org", nonce="...",
uri="/papers/", response="...", opaque="..." uri="/papers/", response="...", opaque="..."
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:propfind xmlns:D="DAV:"> <D:propfind xmlns:D="DAV:">
<D:prop> <D:prop>
skipping to change at line 1202 skipping to change at line 1220
>> Response << >> Response <<
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:multistatus xmlns:D="DAV:"> <D:multistatus xmlns:D="DAV:">
<D:response> <D:response>
<D:href>http://www.example.com/papers/</D:href>
Clemm, Hopkins, Sedlar, Whitehead [Page 25]
<D:href>http://www.webdav.org/papers/</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<D:acl> <D:acl>
<D:ace> <D:ace>
<D:principal> <D:principal>
<D:href>http://www.webdav.org/acl/groups/maintainers</D:href> <D:href>http://www.example.com/acl/groups/maintainers</D:href>
</D:principal> </D:principal>
<D:grant> <D:grant>
<D:privilege> <D:write/> </D:privilege> <D:privilege> <D:write/> </D:privilege>
</D:grant> </D:grant>
</D:ace> </D:ace>
<D:ace> <D:ace>
<D:principal> <D:principal>
<D:all/> <D:all/>
</D:principal> </D:principal>
<D:grant> <D:grant>
<D:privilege> <D:read/> </D:privilege> <D:privilege> <D:read/> </D:privilege>
</D:grant> </D:grant>
</D:ace> </D:ace>
</D:acl> </D:acl>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
</D:multistatus> </D:multistatus>
5.5 DAV:acl-semantics Clemm, et al. [Page 23]
5.5 DAV: acl-restrictions
This is a protected property that defines the ACL semantics of the This protected property defines the types of ACLs supported by this
ACEs specified in the DAV:acl property of this resource. These server, to avoid clients needlessly getting errors. When a client
semantics define how multiple ACEs that match the current user are tries to set an ACL via the ACL method, the server may reject the
combined, what are the constraints on how ACEs can be ordered, and attempt to set the ACL as specified. The following properties
which principals must have an ACE. A client user interface could indicate the restrictions the client must observe before setting an
use the value of this property to provide feedback to a human ACL:
operator concerning the impact of proposed changes to an ACL.
Alternately, a client can use this property to help it determine,
before submitting an ACL method invocation, what ACL changes it
needs to make to accomplish a specific goal (or whether that goal
is even achievable on this server).
Since it is not practical to require all implementations to use the <grant-only> Deny ACEs are not supported
same ACL semantics, the DAV:acl-semantics property is used to
identify the ACL semantics for a particular resource. The DAV:acl-
semantics element is defined in Section 6.
Clemm, Hopkins, Sedlar, Whitehead [Page 26] <no-invert> Inverted ACEs are not supported
5.5.1 Example: Retrieving DAV:acl-semantics
<deny-before-grant> All deny ACEs must occur before any grant
ACEs
<required-principal> Indicates which principals are
required to be present
<!ELEMENT acl-restrictions (grant-only?, no-invert?, deny-before-grant?,
required-principal?)>
5.5.1DAV:grant-only
This element indicates that ACEs with deny clauses are not allowed.
<!ELEMENT grant-only EMPTY>
5.5.2DAV:no-invert ACE Constraint
This element indicates that ACEs with the <invert> element are not
allowed.
<!ELEMENT no-invert EMPTY>
5.5.3DAV:deny-before-grant
This element indicates that all deny ACEs must precede all grant
ACEs.
<!ELEMENT deny-before-grant EMPTY>
5.5.4Required Principals
The required principal elements identify which principals must have
an ACE defined in the ACL.
<!ELEMENT required-principal
(all? | authenticated? | unauthenticated? | self? | href* | property*)>
Clemm, et al. [Page 24]
For example, the following element requires that the ACL contain a
DAV:owner property ACE:
<D:required-principal xmlns:D="DAV:">
<D:property> <D:owner/> </D:property>
</D:required-principal>
Example: Retrieving DAV:acl-restrictions
In this example, the client requests the value of the DAV:acl- In this example, the client requests the value of the DAV:acl-
semantics property. Digest authentication provides credentials for restrictions property. Digest authentication provides credentials
the principal operating the client. In this example, the ACE for the principal operating the client.
combination semantics are DAV:first-match, described in Section
6.1.1, the ACE ordering semantics are not specified (some value
other than DAV:deny-before-grant, described in Section 6.2.1), the
DAV:allowed-ace element states that only one ACE is permitted for
each principal, and an ACE describing the privileges granted the
DAV:all principal must exist in every ACL.
>> Request << >> Request <<
PROPFIND /papers/ HTTP/1.1 PROPFIND /papers/ HTTP/1.1
Host: www.webdav.org Host: www.example.com
Content-type: text/xml; charset="utf-8" Content-type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
Depth: 0 Depth: 0
Authorization: Digest username="srcarter", Authorization: Digest username="srcarter",
realm="srcarter@webdav.org", nonce="...", realm="srcarter@webdav.org", nonce="...",
uri="/papers/", response="...", opaque="..." uri="/papers/", response="...", opaque="..."
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:propfind xmlns:D="DAV:"> <D:propfind xmlns:D="DAV:">
<D:prop> <D:prop>
<D:acl-semantics/> <D:acl-restrictions/>
</D:prop> </D:prop>
</D:propfind> </D:propfind>
>> Response << >> Response <<
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:multistatus xmlns:D="DAV:"> <D:multistatus xmlns:D="DAV:">
<D:response> <D:response>
<D:href>http://www.webdav.org/papers/</D:href> <D:href>http://www.example.com/papers/</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<D:acl-semantics> <D:acl-restrictions>
<D:ace-combination>
<D:first-match/>
</D:ace-combination>
Clemm, Hopkins, Sedlar, Whitehead [Page 27]
<D:ace-ordering/>
<D:allowed-ace>
<D:principal-only-one-ace/> <D:principal-only-one-ace/>
</D:allowed-ace>
<D:required-principal> <D:required-principal>
<D:all/> <D:all/>
</D:required-principal> </D:required-principal>
</D:acl-semantics> </D:acl-restrictions>
Clemm, et al. [Page 25]
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
<D:response> <D:response>
</D:multistatus> </D:multistatus>
5.6 DAV:inherited-acl-set 5.6 DAV:inherited-acl-set
This protected property contains a set of URLs that identify other This protected property contains a set of URLs that identify other
resources that also control the access to this resource. To have a resources that also control the access to this resource. To have a
privilege on a resource, not only must the ACL on that resource privilege on a resource, not only must the ACL on that resource
(specified in the DAV:acl property of that resource) grant the (specified in the DAV:acl property of that resource) grant the
privilege, but so must the ACL of each resource identified in the privilege, but so must the ACL of each resource identified in the
DAV:inherited-acl-set property of that resource. Effectively, the DAV:inherited-acl-set property of that resource. Effectively, the
privileges granted by the current ACL are ANDed with the privileges privileges granted by the current ACL are ANDed with the privileges
granted by each inherited ACL. granted by each inherited ACL.
<!ELEMENT inherited-acl-set (href*)> <!ELEMENT inherited-acl-set (href*)>
Note that the ACL semantics of a resource are specified in the
DAV:acl-semantics property of that resource, and therefore each
inherited ACL can have different ACL semantics.
5.7 DAV:principal-collection-set 5.7 DAV:principal-collection-set
This protected property of a resource contains a set of URLs that This protected property of a resource contains a set of URLs that
identify the root collections that contain the principals that are identify the root collections that contain the principals that are
available on the server that implements this resource. A WebDAV available on the server that implements this resource. A WebDAV
Access Control Protocol user agent could use the contents of Access Control Protocol user agent could use the contents of
DAV:principal-collection-set to retrieve the DAV:displayname DAV:principal-collection-set to retrieve the DAV:displayname
property (specified in Section 13.2 of [RFC2518]) of all principals property (specified in Section 13.2 of [RFC2518]) of all principals
on that server, thereby yielding human-readable names for each on that server, thereby yielding human-readable names for each
principal that could be displayed in a user interface. principal that could be displayed in a user interface.
<!ELEMENT principal-collection-set (href*)> <!ELEMENT principal-collection-set (href*)>
Since different servers can control different parts of the URL Since different servers can control different parts of the URL
namespace, different resources on the same host MAY have different namespace, different resources on the same host MAY have different
DAV:principal-collection-set values. The collections specified in DAV:principal-collection-set values. The collections specified in
the DAV:principal-collection-set MAY be located on different hosts the DAV:principal-collection-set MAY be located on different hosts
from the resource. The URLs in DAV:principal-collection-set SHOULD from the resource. The URLs in DAV:principal-collection-set SHOULD
Clemm, Hopkins, Sedlar, Whitehead [Page 28]
be http or https scheme URLs. For security and scalability reasons, be http or https scheme URLs. For security and scalability reasons,
a server MAY report only a subset of the entire set of known a server MAY report only a subset of the entire set of known
principal collections, and therefore clients should not assume they principal collections, and therefore clients should not assume they
have retrieved an exhaustive listing. Additionally, a server MAY have retrieved an exhaustive listing. Additionally, a server MAY
elect to report none of the principal collections it knows about, elect to report none of the principal collections it knows about,
in which case the property value would be empty. in which case the property value would be empty.
The value of DAV:principal-collection-set gives the scope of the The value of DAV:principal-collection-set gives the scope of the
DAV:principal-property-search REPORT (defined in Section 9.4). DAV:principal-property-search REPORT (defined in Section 9.4).
Clients use the DAV:principal-property-search REPORT to populate Clients use the DAV:principal-property-search REPORT to populate
their user interface with a list of principals. Therefore, servers their user interface with a list of principals. Therefore, servers
that limit a client's ability to obtain principal information will that limit a client's ability to obtain principal information will
interfere with the client's ability to manipulate access control interfere with the client's ability to manipulate access control
Clemm, et al. [Page 26]
lists, due to the difficulty of getting the URL of a principal for lists, due to the difficulty of getting the URL of a principal for
use in an ACE. use in an ACE.
5.7.1 Example: Retrieving DAV:principal-collection-set 5.7.1 Example: Retrieving DAV:principal-collection-set
In this example, the client requests the value of the In this example, the client requests the value of the
DAV:principal-collection-set property on the collection resource DAV:principal-collection-set property on the collection resource
identified by URL http://www.webdav.org/papers/. The property identified by URL http://www.example.com/papers/. The property
contains the two URLs, http://www.webdav.org/acl/users/ and contains the two URLs, http://www.example.com/acl/users/ and
http://www.webdav.org/acl/groups/, both wrapped in DAV:href XML http://www.example.com/acl/groups/, both wrapped in DAV:href XML
elements. Digest authentication provides credentials for the elements. Digest authentication provides credentials for the
principal operating the client. principal operating the client.
The client might reasonably follow this request with two separate The client might reasonably follow this request with two separate
PROPFIND requests to retrieve the DAV:displayname property of the PROPFIND requests to retrieve the DAV:displayname property of the
members of the two collections (/acl/users and /acl/groups). This members of the two collections (/acl/users and /acl/groups). This
information could be used when displaying a user interface for information could be used when displaying a user interface for
creating access control entries. creating access control entries.
>> Request << >> Request <<
PROPFIND /papers/ HTTP/1.1 PROPFIND /papers/ HTTP/1.1
Host: www.webdav.org Host: www.example.com
Content-type: text/xml; charset="utf-8" Content-type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
Depth: 0 Depth: 0
Authorization: Digest username="yarong", Authorization: Digest username="yarong",
realm="yarong@webdav.org", nonce="...", realm="yarong@webdav.org", nonce="...",
uri="/papers/", response="...", opaque="..." uri="/papers/", response="...", opaque="..."
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:propfind xmlns:D="DAV:"> <D:propfind xmlns:D="DAV:">
<D:prop> <D:prop>
<D:principal-collection-set/> <D:principal-collection-set/>
</D:prop> </D:prop>
</D:propfind> </D:propfind>
Clemm, Hopkins, Sedlar, Whitehead [Page 29]
>> Response << >> Response <<
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:multistatus xmlns:D="DAV:"> <D:multistatus xmlns:D="DAV:">
<D:response> <D:response>
<D:href>http://www.webdav.org/papers/</D:href> <D:href>http://www.example.com/papers/</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<D:principal-collection-set> <D:principal-collection-set>
<D:href>http://www.webdav.org/acl/users/</D:href> <D:href>http://www.example.com/acl/users/</D:href>
<D:href>http://www.webdav.org/acl/groups/</D:href>
Clemm, et al. [Page 27]
<D:href>http://www.example.com/acl/groups/</D:href>
</D:principal-collection-set> </D:principal-collection-set>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
</D:multistatus> </D:multistatus>
5.8 Example: PROPFIND to retrieve access control properties 5.8 Example: PROPFIND to retrieve access control properties
The following example shows how access control information can be The following example shows how access control information can be
retrieved by using the PROPFIND method to fetch the values of the retrieved by using the PROPFIND method to fetch the values of the
DAV:owner, DAV:supported-privilege-set, DAV:current-user-privilege- DAV:owner, DAV:supported-privilege-set, DAV:current-user-privilege-
set, and DAV:acl properties. set, and DAV:acl properties.
>> Request << >> Request <<
PROPFIND /top/container/ HTTP/1.1 PROPFIND /top/container/ HTTP/1.1
Host: www.foo.org Host: www.example.com
Content-type: text/xml; charset="utf-8" Content-type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
Depth: 0 Depth: 0
Authorization: Digest username="ejw", Authorization: Digest username="ejw",
realm="users@foo.org", nonce="...", realm="users@foo.org", nonce="...",
uri="/top/container/", response="...", opaque="..." uri="/top/container/", response="...", opaque="..."
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:propfind xmlns:D="DAV:"> <D:propfind xmlns:D="DAV:">
<D:prop> <D:prop>
<D:owner/> <D:owner/>
<D:supported-privilege-set/> <D:supported-privilege-set/>
<D:current-user-privilege-set/> <D:current-user-privilege-set/>
Clemm, Hopkins, Sedlar, Whitehead [Page 30]
<D:acl/> <D:acl/>
</D:prop> </D:prop>
</D:propfind> </D:propfind>
>> Response << >> Response <<
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:multistatus <D:multistatus
xmlns:D="DAV:" xmlns:D="DAV:"
xmlns:A="http://www.webdav.org/acl/"> <D:response> xmlns:A="http://www.example.com/acl/"> <D:response>
<D:href>http://www.foo.org/top/container/</D:href> <D:href>http://www.example.com/top/container/</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<D:owner> <D:owner>
<D:href>http://www.foo.org/users/gclemm</D:href> </D:owner> <D:href>http://www.example.com/users/gclemm</D:href> </D:owner>
<D:supported-privilege-set> <D:supported-privilege-set>
<D:supported-privilege> <D:supported-privilege>
<D:privilege> <D:all/> </D:privilege> <D:privilege> <D:all/> </D:privilege>
Clemm, et al. [Page 28]
<D:abstract/> <D:abstract/>
<D:description xml:lang="en">Any operation</D:description> <D:description xml:lang="en">Any operation</D:description>
<D:supported-privilege> <D:supported-privilege>
<D:privilege> <D:read/> </D:privilege> <D:privilege> <D:read/> </D:privilege>
<D:description xml:lang="en">Read any <D:description xml:lang="en">Read any object</D:description>
object</D:description>
</D:supported-privilege> </D:supported-privilege>
<D:supported-privilege> <D:supported-privilege>
<D:privilege> <D:write/> </D:privilege> <D:privilege> <D:write/> </D:privilege>
<D:abstract/> <D:abstract/>
<D:description xml:lang="en">Write any <D:description xml:lang="en">Write any object</D:description>
object</D:description>
<D:supported-privilege> <D:supported-privilege>
<D:privilege> <A:create/> </D:privilege> <D:privilege> <A:create/> </D:privilege>
<D:description xml:lang="en">Create an <D:description xml:lang="en">Create an object</D:description>
object</D:description>
</D:supported-privilege> </D:supported-privilege>
<D:supported-privilege> <D:supported-privilege>
<D:privilege> <A:update/> </D:privilege> <D:privilege> <A:update/> </D:privilege>
<D:description xml:lang="en">Update an <D:description xml:lang="en">Update an object</D:description>
object</D:description>
</D:supported-privilege> </D:supported-privilege>
<D:supported-privilege> <D:supported-privilege>
<D:privilege> <A:delete/> </D:privilege> <D:privilege> <A:delete/> </D:privilege>
<D:description xml:lang="en">Delete an <D:description xml:lang="en">Delete an object</D:description>
object</D:description>
Clemm, Hopkins, Sedlar, Whitehead [Page 31]
</D:supported-privilege> </D:supported-privilege>
</D:supported-privilege> </D:supported-privilege>
<D:supported-privilege> <D:supported-privilege>
<D:privilege> <D:read-acl/> </D:privilege> <D:privilege> <D:read-acl/> </D:privilege>
<D:description xml:lang="en">Read the ACL</D:description> <D:description xml:lang="en">Read the ACL</D:description>
</D:supported-privilege> </D:supported-privilege>
<D:supported-privilege> <D:supported-privilege>
<D:privilege> <D:write-acl/> </D:privilege> <D:privilege> <D:write-acl/> </D:privilege>
<D:description xml:lang="en">Write the <D:description xml:lang="en">Write the ACL</D:description>
ACL</D:description>
</D:supported-privilege> </D:supported-privilege>
</D:supported-privilege> </D:supported-privilege>
</D:supported-privilege-set> </D:supported-privilege-set>
<D:current-user-privilege-set> <D:current-user-privilege-set>
<D:privilege> <D:read/> </D:privilege> <D:privilege> <D:read/> </D:privilege>
<D:privilege> <D:read-acl/> </D:privilege> <D:privilege> <D:read-acl/> </D:privilege>
</D:current-user-privilege-set> </D:current-user-privilege-set>
<D:acl> <D:acl>
<D:ace> <D:ace>
<D:principal> <D:principal>
<D:href>http://www.foo.org/users/esedlar</D:href> <D:href>http://www.example.com/users/esedlar</D:href>
</D:principal> </D:principal>
<D:grant> <D:grant>
<D:privilege> <D:read/> </D:privilege> <D:privilege> <D:read/> </D:privilege>
<D:privilege> <D:write/> </D:privilege> <D:privilege> <D:write/> </D:privilege>
<D:privilege> <D:read-acl/> </D:privilege> </D:grant> <D:privilege> <D:read-acl/> </D:privilege> </D:grant>
</D:ace> </D:ace>
<D:ace> <D:ace>
<D:principal> <D:principal>
<D:href>http://www.foo.org/groups/marketing</D:href> <D:href>http://www.example.com/groups/marketing</D:href>
</D:principal> </D:principal>
<D:deny> <D:deny>
<D:privilege> <D:read/> </D:privilege> </D:deny> <D:privilege> <D:read/> </D:privilege> </D:deny>
</D:ace> </D:ace>
Clemm, et al. [Page 29]
<D:ace> <D:ace>
<D:principal> <D:principal>
<D:property> <D:owner/> </D:property> </D:principal> <D:property> <D:owner/> </D:property> </D:principal>
<D:grant> <D:grant>
<D:privilege> <D:read-acl/> </D:privilege> <D:privilege> <D:read-acl/> </D:privilege>
<D:privilege> <D:write-acl/> </D:privilege> </D:grant> <D:privilege> <D:write-acl/> </D:privilege> </D:grant>
</D:ace> </D:ace>
<D:ace> <D:ace>
<D:principal> <D:all/> </D:principal> <D:principal> <D:all/> </D:principal>
<D:grant> <D:grant>
<D:privilege> <D:read/> </D:privilege></D:grant> <D:privilege> <D:read/> </D:privilege></D:grant>
<D:inherited> <D:inherited>
<D:href>http://www.foo.org/top</D:href> </D:inherited> <D:href>http://www.example.com/top</D:href> </D:inherited>
</D:ace> </D:acl> </D:ace> </D:acl>
Clemm, Hopkins, Sedlar, Whitehead [Page 32]
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:response> </D:multistatus> </D:propstat> </D:response> </D:multistatus>
The value of the DAV:owner property is a single DAV:href XML The value of the DAV:owner property is a single DAV:href XML
element containing the URL of the principal that owns this element containing the URL of the principal that owns this
resource. resource.
The value of the DAV:supported-privilege-set property is a tree of The value of the DAV:supported-privilege-set property is a tree of
supported privileges (using "[XML Namespace , localname]" to supported privileges (using "[XML Namespace , localname]" to
identify each privilege): identify each privilege):
[DAV:, all] (aggregate, abstract) [DAV:, all] (aggregate, abstract)
| |
+-- [DAV:, read] +-- [DAV:, read]
+-- [DAV:, write] (aggregate, abstract) +-- [DAV:, write] (aggregate, abstract)
| |
+-- [http://www.webdav.org/acl, create] +-- [http://www.example.com/acl, create]
+-- [http://www.webdav.org/acl, update] +-- [http://www.example.com/acl, update]
+-- [http://www.webdav.org/acl, delete] +-- [http://www.example.com/acl, delete]
+-- [DAV:, read-acl] +-- [DAV:, read-acl]
+-- [DAV:, write-acl] +-- [DAV:, write-acl]
The DAV:current-user-privilege-set property contains two The DAV:current-user-privilege-set property contains two
privileges, DAV:read, and DAV:read-acl. This indicates that the privileges, DAV:read, and DAV:read-acl. This indicates that the
current authenticated user only has the ability to read the current authenticated user only has the ability to read the
resource, and read the DAV:acl property on the resource. resource, and read the DAV:acl property on the resource.
The DAV:acl property contains a set of four ACEs: The DAV:acl property contains a set of four ACEs:
ACE #1: The principal identified by the URL ACE #1: The principal identified by the URL
http://www.foo.org/users/esedlar is granted the DAV:read, http://www.example.com/users/esedlar is granted the DAV:read,
DAV:write, and DAV:read-acl privileges. DAV:write, and DAV:read-acl privileges.
ACE #2: The principals identified by the URL ACE #2: The principals identified by the URL
http://www.foo.org/groups/marketing are denied the DAV:read http://www.example.com/groups/marketing are denied the DAV:read
privilege. In this example, the principal URL identifies a group. privilege. In this example, the principal URL identifies a group.
Clemm, et al. [Page 30]
ACE #3: In this ACE, the principal is a property principal, ACE #3: In this ACE, the principal is a property principal,
specifically the DAV:owner property. When evaluating this ACE, the specifically the DAV:owner property. When evaluating this ACE, the
value of the DAV:owner property is retrieved, and is examined to value of the DAV:owner property is retrieved, and is examined to
see if it contains a DAV:href XML element. If so, the URL within see if it contains a DAV:href XML element. If so, the URL within
the DAV:href element is read, and identifies a principal. In this the DAV:href element is read, and identifies a principal. In this
ACE, the owner is granted DAV:read-acl, and DAV:write-acl ACE, the owner is granted DAV:read-acl, and DAV:write-acl
privileges. privileges.
Clemm, Hopkins, Sedlar, Whitehead [Page 33]
ACE #4: This ACE grants the DAV:all principal (all users) the ACE #4: This ACE grants the DAV:all principal (all users) the
DAV:read privilege. This ACE is inherited from the resource DAV:read privilege. This ACE is inherited from the resource
http://www.foo.org/top, the parent collection of this resource. http://www.example.com/top, the parent collection of this resource.
6 ACL SEMANTICS
The ACL semantics define how multiple ACEs that match the current
user are combined, what are the constraints on how ACEs can be
ordered, and which principals must have an ACE.
<!ELEMENT acl-semantics (ace-combination?, ace-ordering?, allowed-
ace?, required-principal?)>
6.1 ACE Combination
The DAV:ace-combination element defines how privileges from
multiple ACEs that match the current user will be combined to
determine the access privileges for that user. Multiple ACEs may
match the same user because the same principal can appear in
multiple ACEs, because multiple principals can identify the same
user, and because one principal can be a member of another
principal.
<!ELEMENT ace-combination
(first-match | all-grant-before-any-deny | specific-deny-
overrides-grant)>
6.1.1 DAV:first-match ACE Combination
The ACEs are evaluated in the order in which they appear in the
ACL. If the first ACE that matches the current user does not grant
all the privileges needed for the request, the request MUST fail.
<!ELEMENT first-match EMPTY>
6.1.2 DAV:all-grant-before-any-deny ACE Combination
The ACEs are evaluated in the order in which they appear in the
ACL. If an evaluated ACE denies a privilege needed for the
request, the request MUST fail. If all ACEs have been evaluated
without the user being granted all privileges needed for the
request, the request MUST fail.
<!ELEMENT all-grant-before-any-deny EMPTY>
Clemm, Hopkins, Sedlar, Whitehead [Page 34]
6.1.3 DAV:specific-deny-overrides-grant ACE Combination
All ACEs in the ACL are evaluated. An "individual ACE" is one
whose principal matches the current user. A "group ACE" is one
whose principal is a group that has a member that matches the
current user. A privilege is granted if it is granted by an
individual ACE and not denied by an individual ACE, or if it is
granted by a group ACE and not denied by an individual or group
ACE. A request MUST fail if any of its needed privileges are not
granted.
<!ELEMENT specific-deny-overrides-grant EMPTY>
6.2 ACE Ordering
The DAV:ace-ordering element defines a constraint on how the ACEs
can be ordered in the ACL.
<!ELEMENT ace-ordering (deny-before-grant)? >
6.2.1 DAV:deny-before-grant ACE Ordering
This element indicates that all deny ACEs must precede all grant
ACEs.
<!ELEMENT deny-before-grant EMPTY>
6.3 Allowed ACE
The DAV:allowed-ace XML element specifies constraints on what kinds
of ACEs are allowed in an ACL.
<!ELEMENT allowed-ace (principal-only-one-ace | grant-only |
no-invert | no-acl-inherit)*>
6.3.1 DAV:principal-only-one-ace ACE Constraint
This element indicates that a principal can appear in only one ACE
per resource.
<!ELEMENT principal-only-one-ace EMPTY>
6.3.2 DAV:grant-only ACE Constraint
This element indicates that ACEs with deny clauses are not allowed.
<!ELEMENT grant-only EMPTY>
Clemm, Hopkins, Sedlar, Whitehead [Page 35]
6.3.3 DAV:no-invert ACE Constraint
This element indicates that ACEs with the <invert> element are not
allowed.
<!ELEMENT no-invert EMPTY> 6 ACL EVALUATION
6.4 Required Principals WebDAV ACLs are evaluated in similar manner as ACLs on Windows NT
and in NFSv4 [NFSV4]). An ACL is evaluated to determine whether or
not access will be granted for a WebDAV request. ACEs are
maintained in a particular order, and are evaluated until all of
the permissions required by the current request have been granted,
at which point the ACL evaluation is terminated and access is
granted. If, during ACL evaluation, a <deny> ACE (matching the
current user) is encountered for a privilege which has not yet been
granted, the ACL evaluation is terminated and access is denied.
Failure to have all required privileges granted results in access
being denied.
The required principal elements identify which principals must have Note that the semantics of many other existing ACL systems may be
an ACE defined in the ACL. represented via this mechanism, by mixing deny and grant ACEs. For
example, consider the standard "rwx" privilege scheme used by UNIX.
In this scheme, if the current user is the owner of the file,
access is granted if the corresponding privilege bit is set and
denied if not set, regardless of the permissions set on the file’s
group and for the world. An ACL for UNIX permissions of "r--rw-r--
"might be constructed like:
<!ELEMENT required-principal <D:acl>
(all? | authenticated? | unauthenticated? | self? | href* | <D:ace>
property*)> <D:principal><D:property><D:owner/></D:property></D:principal>
<D:grant><D:privilege><D:read/></D:privilege></D:grant>
</D:ace>
<D:ace>
<D:principal><D:property><D:owner/></D:property></D:principal>
<D:deny><D:privilege><D:all/></D:privilege></D:deny>
</D:ace>
<D:ace>
<D:principal><D:property><D:group/></D:property></D:principal>
<D:grant><D:privilege><D:read/></D:privilege>
<D:privilege><D:write/></D:privilege></D:grant>
</D:ace>
<D:ace>
<D:principal><D:property><D:group/></D:property></D:principal>
For example, the following element requires that the ACL contain a Clemm, et al. [Page 31]
DAV:owner property ACE: <D:deny><D:privilege><D:all/></D:privilege></D:deny>
</D:ace>
<D:ace>
<D:principal><D:all></D:principal>
<D:grant><D:privilege><D:read/></D:privilege></D:grant>
</D:ace>
</D:acl>
and the <acl-restrictions> would be defined as:
<D:required-principal xmlns:D="DAV:"> <D:no-invert/><D:principal-only-one-ace/>
<D:required-principal>
<D:all/>
<D:property> <D:owner/> </D:property> <D:property> <D:owner/> </D:property>
<D:property><D:group/><D:group/>
</D:required-principal> </D:required-principal>
Note that the client can still get errors from a UNIX server in
spite of obeying the <acl-restrictions>, including <D:allowed-
principal> (adding an ACE specifying a principal other than the
ones in the ACL above) or <D:ace-conflict> (by trying to reorder
the ACEs in the example above), as these particular implementation
semantics are too complex to be captured with the simple (but
general) declarative restrictions.
7 ACCESS CONTROL AND EXISTING METHODS 7 ACCESS CONTROL AND EXISTING METHODS
This section defines the impact of access control functionality on This section defines the impact of access control functionality on
existing methods. existing methods.
7.1 OPTIONS 7.1 OPTIONS
If the server supports access control, it MUST return "access- If the server supports access control, it MUST return "access-
control" as a field in the DAV response header from an OPTIONS control" as a field in the DAV response header from an OPTIONS
request on any resource implemented by that server. A value of request on any resource implemented by that server. A value of
"access-control" in the DAV header MUST indicate that the server "access-control" in the DAV header MUST indicate that the server
supports all MUST level requirements and REQUIRED features supports all MUST level requirements and REQUIRED features
specified in this document. specified in this document.
7.1.1 Example - OPTIONS 7.1.1 Example - OPTIONS
>> Request << >> Request <<
OPTIONS /foo.html HTTP/1.1 OPTIONS /foo.html HTTP/1.1
Host: www.webdav.org Host: www.example.com
Content-Length: 0 Content-Length: 0
>> Response << >> Response <<
Clemm, et al. [Page 32]
HTTP/1.1 200 OK HTTP/1.1 200 OK
DAV: 1, 2, access-control DAV: 1, 2, access-control
Allow: OPTIONS, GET, PUT, PROPFIND, PROPPATCH, ACL Allow: OPTIONS, GET, PUT, PROPFIND, PROPPATCH, ACL
Clemm, Hopkins, Sedlar, Whitehead [Page 36]
In this example, the OPTIONS response indicates that the server In this example, the OPTIONS response indicates that the server
supports access control and that /foo.html can have its access supports access control and that /foo.html can have its access
control list modified by the ACL method. control list modified by the ACL method.
7.2 MOVE 7.2 MOVE
When a resource is moved from one location to another due to a MOVE When a resource is moved from one location to another due to a MOVE
request, the non-inherited and non-protected ACEs in the DAV:acl request, the non-inherited and non-protected ACEs in the DAV:acl
property of the resource MUST NOT be modified, or the MOVE request property of the resource MUST NOT be modified, or the MOVE request
fails. Handling of inherited and protected ACEs is intentionally fails. Handling of inherited and protected ACEs is intentionally
skipping to change at line 1765 skipping to change at line 1748
7.3 COPY 7.3 COPY
The DAV:acl property on the resource at the destination of a COPY The DAV:acl property on the resource at the destination of a COPY
MUST be the same as if the resource was created by an individual MUST be the same as if the resource was created by an individual
resource creation request (e.g. MKCOL, PUT). Clients wishing to resource creation request (e.g. MKCOL, PUT). Clients wishing to
preserve the DAV:acl property across a copy need to read the preserve the DAV:acl property across a copy need to read the
DAV:acl property prior to the COPY, then perform an ACL operation DAV:acl property prior to the COPY, then perform an ACL operation
on the new resource at the destination to restore, insofar as this on the new resource at the destination to restore, insofar as this
is possible, the original access control list. is possible, the original access control list.
7.4 DELETE 7.4 LOCK
The precise combination of privileges and resources necessary to
permit the DELETE method is intentionally left to the discretion of
each server implementation. It is envisioned that on some servers,
DELETE will require write permission on the collection containing
the resource to be deleted. On other servers, it might also
require write permission on the resource being deleted.
7.5 LOCK
A lock on a resource ensures that only the lock owner can modify A lock on a resource ensures that only the lock owner can modify
ACEs that are not inherited and not protected (these are the only ACEs that are not inherited and not protected (these are the only
ACEs that a client can modify with an ACL request). A lock does not ACEs that a client can modify with an ACL request). A lock does not
protect inherited or protected ACEs, since a client cannot modify protect inherited or protected ACEs, since a client cannot modify
them with an ACL request on that resource. them with an ACL request on that resource.
8 ACCESS CONTROL METHODS 8 ACCESS CONTROL METHODS
8.1 ACL 8.1 ACL
The ACL method modifies the access control list (which can be read The ACL method modifies the access control list (which can be read
via the DAV:acl property) of a resource. Specifically, the ACL via the DAV:acl property) of a resource. Specifically, the ACL
Clemm, Hopkins, Sedlar, Whitehead [Page 37]
method only permits modification to ACEs that are not inherited, method only permits modification to ACEs that are not inherited,
and are not protected. An ACL method invocation modifies all non- and are not protected. An ACL method invocation modifies all non-
inherited and non-protected ACEs in a resource's access control inherited and non-protected ACEs in a resource's access control
list to exactly match the ACEs contained within in the DAV:acl XML list to exactly match the ACEs contained within in the DAV:acl XML
element (specified in Section 5.4) of the request body. An ACL element (specified in Section 5.4) of the request body. An ACL
request body MUST contain only one DAV:acl XML element. Unless the request body MUST contain only one DAV:acl XML element. Unless the
non-inherited and non-protected ACEs of the DAV:acl property of the non-inherited and non-protected ACEs of the DAV:acl property of the
Clemm, et al. [Page 33]
resource can be updated to be exactly the value specified in the resource can be updated to be exactly the value specified in the
ACL request, the ACL request MUST fail. ACL request, the ACL request MUST fail.
It is possible that the ACEs visible to the current user in the It is possible that the ACEs visible to the current user in the
DAV:acl property may only be a portion of the complete set of ACEs DAV:acl property may only be a portion of the complete set of ACEs
on that resource. If this is the case, an ACL request only modifies on that resource. If this is the case, an ACL request only modifies
the set of ACEs visible to the current user, and does not affect the set of ACEs visible to the current user, and does not affect
any non-visible ACE. any non-visible ACE.
In order to avoid overwriting DAV:acl changes by another client, a In order to avoid overwriting DAV:acl changes by another client, a
client SHOULD acquire a WebDAV lock on the resource before client SHOULD acquire a WebDAV lock on the resource before
retrieving the DAV:acl property of a resource that it intends on retrieving the DAV:acl property of a resource that it intends on
updating. updating.
Implementation Note: Two common operations are to add or remove Implementation Note: Two common operations are to add or remove an
an ACE from an existing access control list. To accomplish this, ACE from an existing access control list. To accomplish this, a
a client uses the PROPFIND method to retrieve the value of the client uses the PROPFIND method to retrieve the value of the
DAV:acl property, then parses the returned access control list DAV:acl property, then parses the returned access control list to
to remove all inherited and protected ACEs (these ACEs are remove all inherited and protected ACEs (these ACEs are tagged with
tagged with the DAV:inherited and DAV:protected XML elements). the DAV:inherited and DAV:protected XML elements). In the remaining
In the remaining set of non-inherited, non-protected ACEs, the set of non-inherited, non-protected ACEs, the client can add or
client can add or remove one or more ACEs before submitting the remove one or more ACEs before submitting the final ACE set in the
final ACE set in the request body of the ACL method. request body of the ACL method.
8.1.1 ACL Preconditions 8.1.1 ACL Preconditions
An implementation MAY enforce one or more of the following An implementation MUST enforce the following constraints on an ACL
constraints on an ACL request. If the constraint is violated, a request. If the constraint is violated, a 403 (Forbidden) or 409
403 (Forbidden) or 409 (Conflict) response MUST be returned and the (Conflict) response MUST be returned and the indicated XML element
indicated XML element MUST be returned as a child of a top level MUST be returned as a child of a top level DAV:error element in an
DAV:error element in an XML response body. XML response body.
Though these status elements are generally expressed as empty XML
elements (and are defined as EMPTY in the DTD), implementations MAY
return additional descriptive XML elements as children of the
status element. Clients MUST be able to accept children of these
status elements. Clients that do not understand the additional XML
elements should ignore them.
(DAV:no-ace-conflict): The ACEs submitted in the ACL request MUST (DAV:no-ace-conflict): The ACEs submitted in the ACL request MUST
NOT conflict with each other. What is considered a conflict NOT conflict with each other. This is a catchall error code
depends on the ACL semantics of that resource. indicating that an implementation-specific ACL restriction has been
violated.
(DAV:no-protected-ace-conflict): The ACEs submitted in the ACL (DAV:no-protected-ace-conflict): The ACEs submitted in the ACL
request MUST NOT conflict with the protected ACEs on the resource. request MUST NOT conflict with the protected ACEs on the resource.
For example, if the resource has a protected ACE granting DAV:write For example, if the resource has a protected ACE granting DAV:write
to a given principal, then it would not be consistent if the ACL to a given principal, then it would not be consistent if the ACL
request submitted an ACE denying DAV:write to the same principal. request submitted an ACE denying DAV:write to the same principal.
Clemm, Hopkins, Sedlar, Whitehead [Page 38]
(DAV:no-inherited-ace-conflict): The ACEs submitted in the ACL (DAV:no-inherited-ace-conflict): The ACEs submitted in the ACL
request MUST NOT conflict with the inherited ACEs on the resource. request MUST NOT conflict with the inherited ACEs on the resource.
For example, if the resource inherits an ACE from its parent For example, if the resource inherits an ACE from its parent
Clemm, et al. [Page 34]
collection granting DAV:write to a given principal, then it would collection granting DAV:write to a given principal, then it would
not be consistent if the ACL request submitted an ACE denying not be consistent if the ACL request submitted an ACE denying
DAV:write to the same principal. Note that reporting of this error DAV:write to the same principal. Note that reporting of this error
will be implementation-dependent. Implementations have the choice will be implementation-dependent. Implementations MUST either
to either report this error, or to allow the ACE to be set, and report this error or allow the ACE to be set, and then let normal
then let normal ACE evaluation rules determine whether the new ACE ACE evaluation rules determine whether the new ACE has any impact
has any impact on the privileges available to a specific principal. on the privileges available to a specific principal.
(DAV:limited-number-of-aces): The number of ACEs submitted in the (DAV:limited-number-of-aces): The number of ACEs submitted in the
ACL request MUST NOT exceed the number of ACEs allowed on that ACL request MUST NOT exceed the number of ACEs allowed on that
resource. However, ACL-compliant servers MUST support at least one resource. However, ACL-compliant servers MUST support at least one
ACE granting privileges to a single principal, and one ACE granting ACE granting privileges to a single principal, and one ACE granting
privileges to a group. privileges to a group.
(DAV:deny-before-grant): All non-inherited deny ACEs MUST precede (DAV:deny-before-grant): All non-inherited deny ACEs MUST precede
all non-inherited grant ACEs. all non-inherited grant ACEs.
(DAV:principal-only-one-ace): The ACL request MUST NOT result in
more than one ACE for a given principal. This precondition applies
only when the ACL semantics of the resource includes the
DAV:principal-only-one-ace constraint (defined in Section 6.3.1).
(DAV:grant-only): The ACEs submitted in the ACL request MUST NOT (DAV:grant-only): The ACEs submitted in the ACL request MUST NOT
include a deny ACE. This precondition applies only when the ACL include a deny ACE. This precondition applies only when the ACL
semantics of the resource includes the DAV:grant-only constraint restrictions of the resource include the DAV:grant-only constraint
(defined in Section 6.3.2). (defined in Section 5.5.1).
(DAV:no-invert): The ACL request MUST NOT include a DAV:invert (DAV:no-invert): The ACL request MUST NOT include a DAV:invert
element. This precondition applies only when the ACL semantics of element. This precondition applies only when the ACL semantics of
the resource includes the DAV:no-invert constraint (defined in the resource includes the DAV:no-invert constraint (defined in
Section 6.3.4). Section 6.3.4).
(DAV:no-abstract): The ACL request MUST NOT attempt to grant or (DAV:no-abstract): The ACL request MUST NOT attempt to grant or
deny an abstract privilege (see Section 5.2). deny an abstract privilege (see Section 5.2).
(DAV:not-supported-privilege): The ACEs submitted in the ACL (DAV:not-supported-privilege): The ACEs submitted in the ACL
request MUST be supported by the resource. request MUST be supported by the resource.
(DAV:missing-required-principal): The result of the ACL request (DAV:missing-required-principal): The result of the ACL request
MUST have at least one ACE for each principal identified in a MUST have at least one ACE for each principal identified in a
DAV:required-principal XML element in the ACL semantics of that DAV:required-principal XML element in the ACL semantics of that
resource (see Section 6.3.2). resource (see Section 5.5.4).
(DAV:recognized-principal): Every principal URL in the ACL request (DAV:recognized-principal): Every principal URL in the ACL request
MUST identify a principal resource. MUST identify a principal resource.
Clemm, Hopkins, Sedlar, Whitehead [Page 39]
(DAV:allowed-principal): The principals specified in the ACEs (DAV:allowed-principal): The principals specified in the ACEs
submitted in the ACL request MUST be allowed as principals for the submitted in the ACL request MUST be allowed as principals for the
resource. For example, a server where only authenticated principals resource. For example, a server where only authenticated principals
can access resources would not allow the DAV:all or can access resources would not allow the DAV:all or
DAV:unauthenticated principals to be used in an ACE, since these DAV:unauthenticated principals to be used in an ACE, since these
would allow unauthenticated access to resources. would allow unauthenticated access to resources.
8.1.2 Example: the ACL method 8.1.2 Example: the ACL method
In the following example, user "fielding", authenticated by In the following example, user "fielding", authenticated by
information in the Authorization header, grants the principal information in the Authorization header, grants the principal
identified by the URL http://www.foo.org/users/esedlar (i.e., the identified by the URL http://www.example.com/users/esedlar (i.e.,
user "esedlar") read and write privileges, grants the owner of the
resource read-acl and write-acl privileges, and grants everyone Clemm, et al. [Page 35]
the user "esedlar") read and write privileges, grants the owner of
the resource read-acl and write-acl privileges, and grants everyone
read privileges. read privileges.
>> Request << >> Request <<
ACL /top/container/ HTTP/1.1 ACL /top/container/ HTTP/1.1
Host: www.foo.org Host: www.example.com
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
Authorization: Digest username="fielding", Authorization: Digest username="fielding",
realm="users@foo.org", nonce="...", realm="users@foo.org", nonce="...",
uri="/top/container/", response="...", opaque="..." uri="/top/container/", response="...", opaque="..."
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:acl xmlns:D="DAV:"> <D:acl xmlns:D="DAV:">
<D:ace> <D:ace>
<D:principal> <D:principal>
<D:href>http://www.foo.org/users/esedlar</D:href> <D:href>http://www.example.com/users/esedlar</D:href>
</D:principal> </D:principal>
<D:grant> <D:grant>
<D:privilege> <D:read/> </D:privilege> <D:privilege> <D:read/> </D:privilege>
<D:privilege> <D:write/> </D:privilege> <D:privilege> <D:write/> </D:privilege>
</D:grant> </D:grant>
</D:ace> </D:ace>
<D:ace> <D:ace>
<D:principal> <D:principal>
<D:property> <D:owner/> </D:property> <D:property> <D:owner/> </D:property>
</D:principal> </D:principal>
<D:grant> <D:grant>
<D:privilege> <D:read-acl/> </D:privilege> <D:privilege> <D:read-acl/> </D:privilege>
<D:privilege> <D:write-acl/> </D:privilege> <D:privilege> <D:write-acl/> </D:privilege>
</D:grant> </D:grant>
</D:ace> </D:ace>
<D:ace> <D:ace>
<D:principal> <D:all/> </D:principal> <D:principal> <D:all/> </D:principal>
Clemm, Hopkins, Sedlar, Whitehead [Page 40]
<D:grant> <D:grant>
<D:privilege> <D:read/> </D:privilege> <D:privilege> <D:read/> </D:privilege>
</D:grant> </D:grant>
</D:ace> </D:acl> </D:ace> </D:acl>
>> Response << >> Response <<
HTTP/1.1 200 OK HTTP/1.1 200 OK
8.1.3 Example: ACL method failure due to protected ACE conflict 8.1.3 Example: ACL method failure due to protected ACE conflict
In the following request, user "fielding", authenticated by In the following request, user "fielding", authenticated by
information in the Authorization header, attempts to deny the information in the Authorization header, attempts to deny the
principal identified by the URL http://www.foo.org/users/esedlar principal identified by the URL
(i.e., the user "esedlar") write privileges. Prior to the request, http://www.example.com/users/esedlar (i.e., the user "esedlar")
the DAV:acl property on the resource contained a protected ACE (see write privileges. Prior to the request, the DAV:acl property on the
Section 5.4.3) granting DAV:owner the DAV:read and DAV:write resource contained a protected ACE (see Section 5.4.3) granting
privileges. The principal identified by URL DAV:owner the DAV:read and DAV:write privileges. The principal
http://www.foo.org/users/esedlar is the owner of the resource. The
ACL method invocation fails because the submitted ACE conflicts Clemm, et al. [Page 36]
with the protected ACE, thus violating the semantics of ACE identified by URL http://www.example.com/users/esedlar is the owner
protection. of the resource. The ACL method invocation fails because the
submitted ACE conflicts with the protected ACE, thus violating the
semantics of ACE protection.
>> Request << >> Request <<
ACL /top/container/ HTTP/1.1 ACL /top/container/ HTTP/1.1
Host: www.foo.org Host: www.example.com
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
Authorization: Digest username="fielding", Authorization: Digest username="fielding",
realm="users@foo.org", nonce="...", realm="users@foo.org", nonce="...",
uri="/top/container/", response="...", opaque="..." uri="/top/container/", response="...", opaque="..."
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:acl xmlns:D="DAV:"> <D:acl xmlns:D="DAV:">
<D:ace> <D:ace>
<D:principal> <D:principal>
<D:href>http://www.foo.org/users/esedlar</D:href> <D:href>http://www.example.com/users/esedlar</D:href>
</D:principal> </D:principal>
<D:deny> <D:deny>
<D:privilege> <D:write/> </D:privilege> <D:privilege> <D:write/> </D:privilege>
</D:deny> </D:deny>
</D:ace> </D:ace>
</D:acl> </D:acl>
>> Response << >> Response <<
HTTP/1.1 403 Forbidden HTTP/1.1 403 Forbidden
Clemm, Hopkins, Sedlar, Whitehead [Page 41]
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:error xmlns:D="DAV:"> <D:error xmlns:D="DAV:">
<D:no-protected-ace-conflict/> <D:no-protected-ace-conflict/>
</D:error> </D:error>
8.1.4 Example: ACL method failure due to an inherited ACE conflict 8.1.4 Example: ACL method failure due to an inherited ACE conflict
In the following request, user "ejw", authenticated by information In the following request, user "ejw", authenticated by information
in the Authorization header, tries to change the access control in the Authorization header, tries to change the access control
list on the resource http://www.foo.org/top/index.html. This list on the resource http://www.example.com/top/index.html. This
resource has two inherited ACEs. resource has two inherited ACEs.
Inherited ACE #1 grants the principal identified by URL Inherited ACE #1 grants the principal identified by URL
http://www.foo.org/users/ejw (i.e., the user "ejw") http://www.example.com/users/ejw (i.e., the user "ejw")
http://www.foo.org/privs/write-all and DAV:read-acl privileges. On http://www.example.com/privs/write-all and DAV:read-acl privileges.
this server, http://www.foo.org/privs/write-all is an aggregate On this server, http://www.example.com/privs/write-all is an
privilege containing DAV:write, and DAV:write-acl. aggregate privilege containing DAV:write, and DAV:write-acl.
Inherited ACE #2 grants principal DAV:all the DAV:read privilege. Inherited ACE #2 grants principal DAV:all the DAV:read privilege.
Clemm, et al. [Page 37]
The request attempts to set a (non-inherited) ACE, denying the The request attempts to set a (non-inherited) ACE, denying the
principal identified by the URL http://www.foo.org/users/ejw (i.e., principal identified by the URL http://www.example.com/users/ejw
the user "ejw") DAV:write permission. This conflicts with inherited (i.e., the user "ejw") DAV:write permission. This conflicts with
ACE #1. Note that the decision to report an inherited ACE conflict inherited ACE #1. Note that the decision to report an inherited ACE
is specific to this server implementation. Another server conflict is specific to this server implementation. Another server
implementation could have allowed the new ACE to be set, and then implementation could have allowed the new ACE to be set, and then
used normal ACE evaluation rules to determine whether the new ACE used normal ACE evaluation rules to determine whether the new ACE
has any impact on the privileges available to a principal. has any impact on the privileges available to a principal.
>> Request << >> Request <<
ACL /top/index.html HTTP/1.1 ACL /top/index.html HTTP/1.1
Host: www.foo.org Host: www.example.com
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
Authorization: Digest username="ejw", Authorization: Digest username="ejw",
realm="users@foo.org", nonce="...", realm="users@foo.org", nonce="...",
uri="/top/index.html", response="...", opaque="..." uri="/top/index.html", response="...", opaque="..."
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:acl xmlns:D="DAV:" xmlns:F="http://www.foo.org/privs/"> <D:acl xmlns:D="DAV:" xmlns:F="http://www.example.com/privs/">
<D:ace> <D:ace>
<D:principal> <D:principal>
<D:href>http://www.foo.org/users/ejw</D:href> <D:href>http://www.example.com/users/ejw</D:href>
</D:principal> </D:principal>
<D:grant><D:write/></D:grant> <D:grant><D:write/></D:grant>
Clemm, Hopkins, Sedlar, Whitehead [Page 42]
</D:ace> </D:ace>
</D:acl> </D:acl>
>> Response << >> Response <<
HTTP/1.1 403 Forbidden HTTP/1.1 403 Forbidden
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:error xmlns:D="DAV:"> <D:error xmlns:D="DAV:">
<D:no-inherited-ace-conflict xmlns:D="DAV:"/> <D:no-inherited-ace-conflict xmlns:D="DAV:"/>
</D:error> </D:error>
8.1.5 Example: ACL method failure due to an attempt to set grant and 8.1.5Example: ACL method failure due to an attempt to set grant and deny in a
deny in a single ACE. single ACE.
In this example, user "ygoland", authenticated by information in In this example, user "ygoland", authenticated by information in
the Authorization header, tries to change the access control list the Authorization header, tries to change the access control list
on the resource http://www.foo.org/diamond/engagement-ring.gif. The on the resource http://www.example.com/diamond/engagement-ring.gif.
ACL request includes a single, syntactically and semantically The ACL request includes a single, syntactically and semantically
incorrect ACE, which attempts to grant the group identified by the incorrect ACE, which attempts to grant the group identified by the
URL http://www.foo.org/users/friends DAV:read privilege and deny URL http://www.example.com/users/friends DAV:read privilege and
the principal identified by URL http://www.foo.org/users/ygoland-so deny the principal identified by URL
(i.e., the user "ygoland-so") DAV:read privilege. However, it is http://www.example.com/users/ygoland-so (i.e., the user "ygoland-
illegal to have multiple principal elements, as well as both a so") DAV:read privilege. However, it is illegal to have multiple
grant and deny element in the same ACE, so the request fails due to principal elements, as well as both a grant and deny element in the
poor syntax. same ACE, so the request fails due to poor syntax.
Clemm, et al. [Page 38]
>> Request << >> Request <<
ACL /diamond/engagement-ring.gif HTTP/1.1 ACL /diamond/engagement-ring.gif HTTP/1.1
Host: www.foo.org Host: www.example.com
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
Authorization: Digest username="ygoland", Authorization: Digest username="ygoland",
realm="users@foo.org", nonce="...", realm="users@foo.org", nonce="...",
uri="/diamond/engagement-ring.gif", response="...", opaque="..." uri="/diamond/engagement-ring.gif", response="...", opaque="..."
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:acl xmlns:D="DAV:"> <D:acl xmlns:D="DAV:">
<D:ace> <D:ace>
<D:principal> <D:principal>
<D:href>http://www.foo.org/users/friends</D:href> <D:href>http://www.example.com/users/friends</D:href>
</D:principal> </D:principal>
<D:grant><D:read/></D:grant> <D:grant><D:read/></D:grant>
<D:principal> <D:principal>
<D:href>http://www.foo.org/users/ygoland-so</D:href> <D:href>http://www.example.com/users/ygoland-so</D:href>
Clemm, Hopkins, Sedlar, Whitehead [Page 43]
</D:principal> </D:principal>
<D:deny><D:read/></D:deny> <D:deny><D:read/></D:deny>
</D:ace> </D:ace>
</D:acl> </D:acl>
>> Response << >> Response <<
HTTP/1.1 400 Bad Request HTTP/1.1 400 Bad Request
Content-Length: 0 Content-Length: 0
skipping to change at line 2123 skipping to change at line 2098
processing. REPORT is valuable in cases where the server has access processing. REPORT is valuable in cases where the server has access
to all of the information needed to perform the complex request to all of the information needed to perform the complex request
(such as a query), and where it would require multiple requests for (such as a query), and where it would require multiple requests for
the client to retrieve the information needed to perform the same the client to retrieve the information needed to perform the same
request. request.
A server that supports the WebDAV Access Control Protocol MUST A server that supports the WebDAV Access Control Protocol MUST
support the DAV:expand-property report (defined in Section 3.8 of support the DAV:expand-property report (defined in Section 3.8 of
[RFC3253]). [RFC3253]).
Clemm, et al. [Page 39]
9.2 DAV:acl-principal-prop-set Report 9.2 DAV:acl-principal-prop-set Report
The DAV:acl-principal-prop-set report returns, for all principals The DAV:acl-principal-prop-set report returns, for all principals
in the DAV:acl property (of the Request-URI) that are identified by in the DAV:acl property (of the Request-URI) that are identified by
http(s) URLs or by a DAV:property principal, the value of the http(s) URLs or by a DAV:property principal, the value of the
properties specified in the REPORT request body. In the case where properties specified in the REPORT request body. In the case where
a principal URL appears multiple times, the DAV:acl-principal-prop- a principal URL appears multiple times, the DAV:acl-principal-prop-
set report MUST return the properties for that principal only once. set report MUST return the properties for that principal only once.
Support for this report is REQUIRED. Support for this report is REQUIRED.
One expected use of this report is to retrieve the human readable One expected use of this report is to retrieve the human readable
name (found in the DAV:displayname property) of each principal name (found in the DAV:displayname property) of each principal
found in an ACL. This is useful for constructing user interfaces found in an ACL. This is useful for constructing user interfaces
that show each ACE in a human readable form. that show each ACE in a human readable form.
Marshalling Marshalling
Clemm, Hopkins, Sedlar, Whitehead [Page 44]
The request body MUST be a DAV:acl-principal-prop-set XML element. The request body MUST be a DAV:acl-principal-prop-set XML element.
<!ELEMENT acl-principal-prop-set ANY> <!ELEMENT acl-principal-prop-set ANY>
ANY value: a sequence of one or more elements, with at most one ANY value: a sequence of one or more elements, with at most one DAV:prop
DAV:prop element. element.
prop: see RFC 2518, Section 12.11 prop: see RFC 2518, Section 12.11
This report is only defined when the Depth header has value "0"; This report is only defined when the Depth header has value "0";
other values result in a 400 (Bad Request) error response. Note other values result in a 400 (Bad Request) error response. Note
that [RFC3253], Section 3.6, states that if the Depth header is not that [RFC3253], Section 3.6, states that if the Depth header is not
present, it defaults to a value of "0". present, it defaults to a value of "0".
The response body for a successful request MUST be a The response body for a successful request MUST be a
DAV:multistatus XML element (i.e., the response uses the same DAV:multistatus XML element (i.e., the response uses the same
format as the response for PROPFIND). format as the response for PROPFIND). In the case where there are
no response elements, the returned multistatus XML element is
empty.
multistatus: see RFC 2518, Section 12.9 multistatus: see RFC 2518, Section 12.9
The response body for a successful DAV:acl-principal-prop-set The response body for a successful DAV:acl-principal-prop-set
REPORT request MUST contain a DAV:response element for each REPORT request MUST contain a DAV:response element for each
principal identified by an http(s) URL listed in a DAV:principal principal identified by an http(s) URL listed in a DAV:principal
XML element of an ACE within the DAV:acl property of the resource XML element of an ACE within the DAV:acl property of the resource
identified by the Request-URI. identified by the Request-URI.
Postconditions:
(DAV:number-of-matches-within-limits): The number of matching
principals must fall within server-specific, predefined limits. For
example, this condition might be triggered if a search
specification would cause the return of an extremely large number
of responses.
Clemm, et al. [Page 40]
9.2.1 Example: DAV:acl-principal-prop-set Report 9.2.1 Example: DAV:acl-principal-prop-set Report
Resource http://www.webdav.org/index.html has an ACL with three Resource http://www.example.com/index.html has an ACL with three
ACEs: ACEs:
ACE #1: All principals (DAV:all) have DAV:read and DAV:read- ACE #1: All principals (DAV:all) have DAV:read and DAV:read-
current-user-privilege-set access. current-user-privilege-set access.
ACE #2: The principal identified by ACE #2: The principal identified by
http://www.webdav.org/people/gstein (the user "gstein") is granted http://www.example.com/people/gstein (the user "gstein") is granted
DAV:write, DAV:write-acl, DAV:read-acl privileges. DAV:write, DAV:write-acl, DAV:read-acl privileges.
ACE #3: The group identified by ACE #3: The group identified by
http://www.webdav.org/groups/authors (the "authors" group) is http://www.example.com/groups/authors (the "authors" group) is
granted DAV:write and DAV:read-acl privileges. granted DAV:write and DAV:read-acl privileges.
The following example shows a DAV:acl-principal-prop-set report The following example shows a DAV:acl-principal-prop-set report
requesting the DAV:displayname property. It returns the value of requesting the DAV:displayname property. It returns the value of
DAV:displayname for resources http://www.webdav.org/people/gstein DAV:displayname for resources http://www.example.com/people/gstein
and http://www.webdav.org/groups/authors , but not for DAV:all, and http://www.example.com/groups/authors , but not for DAV:all,
since this is not an http(s) URL. since this is not an http(s) URL.
Clemm, Hopkins, Sedlar, Whitehead [Page 45]
>> Request << >> Request <<
REPORT /index.html HTTP/1.1 REPORT /index.html HTTP/1.1
Host: www.webdav.org Host: www.example.com
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
Depth: 0 Depth: 0
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:acl-principal-prop-set xmlns:D="DAV:"> <D:acl-principal-prop-set xmlns:D="DAV:">
<D:prop> <D:prop>
<D:displayname/> <D:displayname/>
</D:prop> </D:prop>
</D:acl-principal-prop-set> </D:acl-principal-prop-set>
>> Response << >> Response <<
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:multistatus xmlns:D="DAV:"> <D:multistatus xmlns:D="DAV:">
<D:response> <D:response>
<D:href>http://www.webdav.org/people/gstein</D:href> <D:href>http://www.example.com/people/gstein</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<D:displayname>Greg Stein</D:displayname> <D:displayname>Greg Stein</D:displayname>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
Clemm, et al. [Page 41]
</D:response> </D:response>
<D:response> <D:response>
<D:href>http://www.webdav.org/groups/authors</D:href> <D:href>http://www.example.com/groups/authors</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<D:displayname>Site authors</D:displayname> <D:displayname>Site authors</D:displayname>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
</D:multistatus> </D:multistatus>
9.3 DAV:principal-match REPORT 9.3 DAV:principal-match REPORT
The DAV:principal-match REPORT is used to identify all members (at The DAV:principal-match REPORT is used to identify all members (at
any depth) of the collection identified by the Request-URI that any depth) of the collection identified by the Request-URI that
match the current user. In particular, if the collection contains match the current user. In particular, if the collection contains
Clemm, Hopkins, Sedlar, Whitehead [Page 46]
principals, the report can be used to identify all members of the principals, the report can be used to identify all members of the
collection that match the current user. Alternatively, if the collection that match the current user. Alternatively, if the
collection contains resources that have a property that identifies collection contains resources that have a property that identifies
a principal (e.g. DAV:owner), the report can be used to identify a principal (e.g. DAV:owner), the report can be used to identify
all members of the collection whose property identifies a principal all members of the collection whose property identifies a principal
that matches the current user. For example, this report can return that matches the current user. For example, this report can return
all of the resources in a collection hierarchy that are owned by all of the resources in a collection hierarchy that are owned by
the current user. Support for this report is REQUIRED. the current user. Support for this report is REQUIRED.
Marshalling: Marshalling:
skipping to change at line 2248 skipping to change at line 2233
principals, the report can be used to identify all members of the principals, the report can be used to identify all members of the
collection that match the current user. Alternatively, if the collection that match the current user. Alternatively, if the
collection contains resources that have a property that identifies collection contains resources that have a property that identifies
a principal (e.g. DAV:owner), the report can be used to identify a principal (e.g. DAV:owner), the report can be used to identify
all members of the collection whose property identifies a principal all members of the collection whose property identifies a principal
that matches the current user. For example, this report can return that matches the current user. For example, this report can return
all of the resources in a collection hierarchy that are owned by all of the resources in a collection hierarchy that are owned by
the current user. Support for this report is REQUIRED. the current user. Support for this report is REQUIRED.
Marshalling: Marshalling:
The request body MUST be a DAV:principal-match XML element. The request body MUST be a DAV:principal-match XML element.
<!ELEMENT principal-match ((principal-property | self), prop?)> <!ELEMENT principal-match ((principal-property | self), prop?)>
<!ELEMENT principal-property ANY> <!ELEMENT principal-property ANY>
ANY value: an element whose value identifies a property. The ANY value: an element whose value identifies a property. The expectation is
expectation is the value of the named property typically contains the value of the named property typically contains an href element that
an href element that contains the URI of a principal contains the URI of a principal
<!ELEMENT self EMPTY> <!ELEMENT self EMPTY>
prop: see RFC 2518, Section 12.11 prop: see RFC 2518, Section 12.11
This report is only defined when the Depth header has value "0"; This report is only defined when the Depth header has value "0";
other values result in a 400 (Bad Request) error response. Note other values result in a 400 (Bad Request) error response. Note
that [RFC3253], Section 3.6, states that if the Depth header is not that [RFC3253], Section 3.6, states that if the Depth header is not
present, it defaults to a value of "0". present, it defaults to a value of "0".
The response body for a successful request MUST be a The response body for a successful request MUST be a
DAV:multistatus XML element. DAV:multistatus XML element. In the case where there are no
response elements, the returned multistatus XML element is empty.
multistatus: see RFC 2518, Section 12.9 multistatus: see RFC 2518, Section 12.9
The response body for a successful DAV:principal-match REPORT The response body for a successful DAV:principal-match REPORT
request MUST contain a DAV:response element for each member of the request MUST contain a DAV:response element for each member of the
collection that matches the current user. When the DAV:principal- collection that matches the current user. When the DAV:principal-
Clemm, et al. [Page 42]
property element is used, a match occurs if the current user is property element is used, a match occurs if the current user is
matched by the principal identified by the URI found in the matched by the principal identified by the URI found in the
DAV:href element of the property identified by the DAV:principal- DAV:href element of the property identified by the DAV:principal-
property element. When the DAV:self element is used in a property element. When the DAV:self element is used in a
DAV:principal-match report issued against a group, it matches a DAV:principal-match report issued against a group, it matches the
member of the group if that child (a principal resource) identifies group if a member identifies the same principal as the current
the same principal as the current user. user.
If DAV:prop is specified in the request body, the properties If DAV:prop is specified in the request body, the properties
specified in the DAV:prop element MUST be reported in the specified in the DAV:prop element MUST be reported in the
DAV:response elements. DAV:response elements.
Clemm, Hopkins, Sedlar, Whitehead [Page 47]
9.3.1 Example: DAV:principal-match REPORT 9.3.1 Example: DAV:principal-match REPORT
The following example identifies the members of the collection The following example identifies the members of the collection
identified by the URL http://www.webdav.org/doc that are owned by identified by the URL http://www.example.com/doc that are owned by
the current user. The current user ("gclemm") is authenticated the current user. The current user ("gclemm") is authenticated
using Digest authentication. using Digest authentication.
>> Request << >> Request <<
REPORT /doc/ HTTP/1.1 REPORT /doc/ HTTP/1.1
Host: www.webdav.org Host: www.example.com
Authorization: Digest username="gclemm", Authorization: Digest username="gclemm",
realm="gclemm@webdav.org", nonce="...", realm="gclemm@webdav.org", nonce="...",
uri="/papers/", response="...", opaque="..." uri="/papers/", response="...", opaque="..."
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
Depth: 0 Depth: 0
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:principal-match xmlns:D="DAV:"> <D:principal-match xmlns:D="DAV:">
<D:principal-property> <D:principal-property>
skipping to change at line 2318 skipping to change at line 2306
>> Response << >> Response <<
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxxx Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:multistatus xmlns:D="DAV:"> <D:multistatus xmlns:D="DAV:">
<D:response> <D:response>
<D:href>http://www.webdav.org/doc/foo.html</D:href> <D:href>http://www.example.com/doc/foo.html</D:href>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:response> </D:response>
<D:response> <D:response>
<D:href>http://www.webdav.org/doc/img/bar.gif</D:href> <D:href>http://www.example.com/doc/img/bar.gif</D:href>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:response> </D:response>
Clemm, et al. [Page 43]
</D:multistatus> </D:multistatus>
9.4 DAV:principal-property-search REPORT 9.4 DAV:principal-property-search REPORT
The DAV:principal-property-search REPORT performs a search for all The DAV:principal-property-search REPORT performs a search for all
principals whose properties contain character data that matches the principals whose properties contain character data that matches the
search criteria specified in the request. One expected use of this search criteria specified in the request. One expected use of this
report is to discover the URL of a principal associated with a report is to discover the URL of a principal associated with a
Clemm, Hopkins, Sedlar, Whitehead [Page 48]
given person or group by searching for them by name. This is done given person or group by searching for them by name. This is done
by searching over DAV:displayname, which is defined on all by searching over DAV:displayname, which is defined on all
principals. principals.
The actual search method (exact matching vs. substring matching vs, The actual search method (exact matching vs. substring matching vs,
prefix-matching, case-sensitivity) deliberately is left to the prefix-matching, case-sensitivity) deliberately is left to the
server implementation to allow implementation on a wide set of server implementation to allow implementation on a wide set of
possible user management systems. In cases where the implementation possible user management systems. In cases where the implementation
of DAV:principal-property-search is not constrained by the of DAV:principal-property-search is not constrained by the
semantics of an underlying user management repository, preferred semantics of an underlying user management repository, preferred
default semantics are caseless substring matches. default semantics are caseless substring matches.
For implementation efficiency, servers do not typically support For implementation efficiency, servers do not typically support
searching on all properties. A client can discover the set of searching on all properties. A client can discover the set of
searchable properties by using the DAV:principal-search-property- searchable properties by using the DAV:principal-search-property-
set REPORT, defined in Section 9.5. set REPORT, defined in Section 9.5.
Support for the DAV:principal-property-search report is REQUIRED. Support for the DAV:principal-property-search report is REQUIRED.
Implementation Note: The value of a WebDAV property is a Implementation Note: The value of a WebDAV property is a sequence
sequence of well-formed XML, and hence can include any character of well-formed XML, and hence can include any character in the
in the Unicode/ISO-10646 standard, that is, most known Unicode/ISO-10646 standard, that is, most known characters in human
characters in human languages. Due to the idiosyncrasies of case languages. Due to the idiosyncrasies of case mapping across human
mapping across human languages, implementation of case- languages, implementation of case-insensitive matching is non-
insensitive matching is non-trivial. Implementors of servers trivial. Implementors of servers that do perform substring matching
that do perform substring matching are strongly encouraged to are strongly encouraged to consult [CaseMap], especially Section
consult [CaseMap], especially Section 2.3 ("Caseless Matching"), 2.3 ("Caseless Matching"), for guidance when implementing their
for guidance when implementing their case-insensitive matching case-insensitive matching algorithms.
algorithms.
Implementation Note: Some implementations of this protocol will Implementation Note: Some implementations of this protocol will use
use an LDAP repository for storage of principal metadata. The an LDAP repository for storage of principal metadata. The schema
schema describing each attribute (akin to a WebDAV property) in describing each attribute (akin to a WebDAV property) in an LDAP
an LDAP repository specifies whether it supports case-sensitive repository specifies whether it supports case-sensitive or caseless
or caseless searching. One of the benefits of leaving the search searching. One of the benefits of leaving the search method to the
method to the discretion of the server implementation is the discretion of the server implementation is the default LDAP
default LDAP attribute search behavior can be used when attribute search behavior can be used when implementing the
implementing the DAV:principal-property-search report. DAV:principal-property-search report.
Marshalling: Marshalling:
The request body MUST be a DAV:principal-property-search XML The request body MUST be a DAV:principal-property-search XML
element containing a search specification and an optional list of element containing a search specification and an optional list of
properties. For every principal that matches the search properties. For every principal that matches the search
specification, the response will contain the value of the requested specification, the response will contain the value of the requested
properties on that principal. properties on that principal.
Clemm, et al. [Page 44]
<!ELEMENT principal-property-search <!ELEMENT principal-property-search
((property-search+), prop?, apply-to-principal-collection-set?) > ((property-search+), prop?, apply-to-principal-collection-set?) >
Clemm, Hopkins, Sedlar, Whitehead [Page 49]
By default, the report searches all members (at any depth) of the By default, the report searches all members (at any depth) of the
collection identified by the Request-URI. If DAV:apply-to- collection identified by the Request-URI. If DAV:apply-to-
principal-collection-set is specified in the request body, the principal-collection-set is specified in the request body, the
request is applied instead to each collection identified by the request is applied instead to each collection identified by the
DAV:prinicipal-collection-set property of the resource identified DAV:prinicipal-collection-set property of the resource identified
by the Request-URI. by the Request-URI.
The DAV:property-search element contains a prop element enumerating The DAV:property-search element contains a prop element enumerating
the properties to be searched and a match element, containing the the properties to be searched and a match element, containing the
search string. search string.
skipping to change at line 2410 skipping to change at line 2398
Multiple property-search elements or multiple elements within a Multiple property-search elements or multiple elements within a
DAV:prop element will be interpreted with a logical AND. DAV:prop element will be interpreted with a logical AND.
This report is only defined when the Depth header has value "0"; This report is only defined when the Depth header has value "0";
other values result in a 400 (Bad Request) error response. Note other values result in a 400 (Bad Request) error response. Note
that [RFC3253], Section 3.6, states that if the Depth header is not that [RFC3253], Section 3.6, states that if the Depth header is not
present, it defaults to a value of "0". present, it defaults to a value of "0".
The response body for a successful request MUST be a The response body for a successful request MUST be a
DAV:multistatus XML element. DAV:multistatus XML element. In the case where there are no
response elements, the returned multistatus XML element is empty.
multistatus: see RFC 2518, Section 12.9 multistatus: see RFC 2518, Section 12.9
The response body for a successful DAV:principal-property-search The response body for a successful DAV:principal-property-search
REPORT request MUST contain a DAV:response element for each REPORT request MUST contain a DAV:response element for each
principal whose property values satisfy the search specification principal whose property values satisfy the search specification
given in DAV:principal-property-search. given in DAV:principal-property-search.
The response body for an unsuccessful DAV:principal-property-search The response body for an unsuccessful DAV:principal-property-search
REPORT request MUST contain, after the XML element indicating the REPORT request MUST contain, after the XML element indicating the
skipping to change at line 2429 skipping to change at line 2418
The response body for an unsuccessful DAV:principal-property-search The response body for an unsuccessful DAV:principal-property-search
REPORT request MUST contain, after the XML element indicating the REPORT request MUST contain, after the XML element indicating the
failed precondition or postcondition, a DAV:prop element containing failed precondition or postcondition, a DAV:prop element containing
the property that caused the pre/postcondition to fail. the property that caused the pre/postcondition to fail.
If DAV:prop is specified in the request body, the properties If DAV:prop is specified in the request body, the properties
specified in the DAV:prop element MUST be reported in the specified in the DAV:prop element MUST be reported in the
DAV:response elements. DAV:response elements.
Preconditions: Preconditions:
(DAV:property-must-be-searchable): All properties specified in the (DAV:property-must-be-searchable): All properties specified in the
DAV:principal-property-search REPORT must be searchable. DAV:principal-property-search REPORT must be searchable.
Clemm, Hopkins, Sedlar, Whitehead [Page 50] Postconditions:
Clemm, et al. [Page 45]
(DAV:number-of-matches-within-limits): The number of matching
principals must fall within server-specific, predefined limits. For
example, this condition might be triggered if a search
specification would cause the return of an extremely large number
of responses.
9.4.1 Matching 9.4.1 Matching
There are several cases to consider when matching strings. The There are several cases to consider when matching strings. The
easiest case is when a property value is "simple" and has only easiest case is when a property value is "simple" and has only
character information item content (see [REC-XML-INFOSET]). For character information item content (see [REC-XML-INFOSET]). For
example, the search string "julian" would match the DAV:displayname example, the search string "julian" would match the DAV:displayname
property with value "Julian Reschke". Note that the on-the-wire property with value "Julian Reschke". Note that the on-the-wire
marshalling of DAV:displayname in this case is: marshalling of DAV:displayname in this case is:
<D:displayname xmlns:D="DAV:">Julian Reschke</D:displayname> <D:displayname xmlns:D="DAV:">Julian Reschke</D:displayname>
The name of the property is encoded into the XML element The name of the property is encoded into the XML element
information item, and the character information item content of the information item, and the character information item content of the
property is "Julian Reschke". property is "Julian Reschke".
A more complicated case occurs when properties have mixed content A more complicated case occurs when properties have mixed content
(that is, compound values consisting of multiple child element (that is, compound values consisting of multiple child element
items, other types of information items, and character information items, other types of information items, and character information
item content). Consider the property "aprop" in the namespace item content). Consider the property "aprop" in the namespace
"http://www.webdav.org/props/", marshalled as: "http://www.example.com/props/", marshalled as:
<W:aprop xmlns:W="http://www.webdav.org/props/"> <W:aprop xmlns:W="http://www.example.com/props/">
{cdata 0}<W:elem1>{cdata 1}</W:elem1> {cdata 0}<W:elem1>{cdata 1}</W:elem1>
<W:elem2>{cdata 2}</W:elem2>{cdata 3} <W:elem2>{cdata 2}</W:elem2>{cdata 3}
</W:aprop> </W:aprop>
In this case, matching is performed on each individual contiguous In this case, matching is performed on each individual contiguous
sequence of character information items. In the example above, a sequence of character information items. In the example above, a
search string would be compared to the four following strings: search string would be compared to the four following strings:
{cdata 0} {cdata 0}
{cdata 1} {cdata 1}
skipping to change at line 2476 skipping to change at line 2474
{cdata 3} {cdata 3}
That is, four individual matches would be performed, one each for That is, four individual matches would be performed, one each for
{cdata 0}, {cdata 1}, {cdata 2}, and {cdata 3}. {cdata 0}, {cdata 1}, {cdata 2}, and {cdata 3}.
9.4.2 Example: successful DAV:principal-property-search REPORT 9.4.2 Example: successful DAV:principal-property-search REPORT
In this example, the client requests the principal URLs of all In this example, the client requests the principal URLs of all
users whose DAV:displayname property contains the substring "doE" users whose DAV:displayname property contains the substring "doE"
and whose "title" property in the namespace and whose "title" property in the namespace
Clemm, et al. [Page 46]
"http://BigCorp.com/ns/" (that is, their professional title) "http://BigCorp.com/ns/" (that is, their professional title)
contains "Sales". In addition, the client requests five properties contains "Sales". In addition, the client requests five properties
to be returned with the matching principals: to be returned with the matching principals:
Clemm, Hopkins, Sedlar, Whitehead [Page 51]
In the DAV: namespace: displayname In the DAV: namespace: displayname
In the http://www.BigCorp.com/ns/ namespace: department, phone, In the http://www.example.com/ns/ namespace: department, phone,
office, salary office, salary
The response shows that two principal resources meet the search The response shows that two principal resources meet the search
specification, "John Doe" and "Zygdoebert Smith". The property specification, "John Doe" and "Zygdoebert Smith". The property
"salary" in namespace "http://www.BigCorp.com/ns/" is not returned, "salary" in namespace "http://www.example.com/ns/" is not returned,
since the principal making the request does not have sufficient since the principal making the request does not have sufficient
access permissions to read this property. access permissions to read this property.
>> Request << >> Request <<
REPORT /users/ HTTP/1.1 REPORT /users/ HTTP/1.1
Host: www.BigCorp.com Host: www.example.com
Content-Type: text/xml; charset=utf-8 Content-Type: text/xml; charset=utf-8
Content-Length: xxxx Content-Length: xxxx
Depth: 0 Depth: 0
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:principal-property-search xmlns:D="DAV:"> <D:principal-property-search xmlns:D="DAV:">
<D:property-search> <D:property-search>
<D:prop> <D:prop>
<D:displayname/> <D:displayname/>
</D:prop> </D:prop>
<D:match>doE</D:match> <D:match>doE</D:match>
</D:property-search> </D:property-search>
<D:property-search> <D:property-search>
<D:prop xmlns:B="http://www.BigCorp.com/ns/"> <D:prop xmlns:B="http://www.example.com/ns/">
<B:title/> <B:title/>
</D:prop> </D:prop>
<D:match>Sales</D:match> <D:match>Sales</D:match>
</D:property-search> </D:property-search>
<D:prop xmlns:B="http://www.BigCorp.com/ns/"> <D:prop xmlns:B="http://www.example.com/ns/">
<D:displayname/> <D:displayname/>
<B:department/> <B:department/>
<B:phone/> <B:phone/>
<B:office/> <B:office/>
<B:salary/> <B:salary/>
</D:prop> </D:prop>
</D:principal-property-search> </D:principal-property-search>
>> Response << >> Response <<
HTTP/1.1 207 Multi-Status HTTP/1.1 207 Multi-Status
Content-Type: text/xml; charset=utf-8 Content-Type: text/xml; charset=utf-8
Content-Length: xxxx Content-Length: xxxx
Clemm, Hopkins, Sedlar, Whitehead [Page 52] Clemm, et al. [Page 47]
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:multistatus xmlns:D="DAV:" xmlns:B="http://BigCorp.com/ns/"> <D:multistatus xmlns:D="DAV:" xmlns:B="http://BigCorp.com/ns/">
<D:response> <D:response>
<D:href>http://www.BigCorp.com/users/jdoe</D:href> <D:href>http://www.example.com/users/jdoe</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<D:displayname>John Doe</D:displayname> <D:displayname>John Doe</D:displayname>
<B:department>Widget Sales</B:department> <B:department>Widget Sales</B:department>
<B:phone>234-4567</B:phone> <B:phone>234-4567</B:phone>
<B:office>209</B:office> <B:office>209</B:office>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<B:salary/> <B:salary/>
</D:prop> </D:prop>
<D:status>HTTP/1.1 403 Forbidden</D:status> <D:status>HTTP/1.1 403 Forbidden</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
<D:response> <D:response>
<D:href>http://www.BigCorp.com/users/zsmith</D:href> <D:href>http://www.example.com/users/zsmith</D:href>
<D:propstat> <D:propstat>
<D:prop> <D:prop>
<D:displayname>Zygdoebert Smith</D:displayname> <D:displayname>Zygdoebert Smith</D:displayname>
<B:department>Gadget Sales</B:department> <B:department>Gadget Sales</B:department>
<B:phone>234-7654</B:phone> <B:phone>234-7654</B:phone>
<B:office>114</B:office> <B:office>114</B:office>
</D:prop> </D:prop>
<D:status>HTTP/1.1 200 OK</D:status> <D:status>HTTP/1.1 200 OK</D:status>
</D:propstat> </D:propstat>
<D:propstat> <D:propstat>
skipping to change at line 2572 skipping to change at line 2571
<B:salary/> <B:salary/>
</D:prop> </D:prop>
<D:status>HTTP/1.1 403 Forbidden</D:status> <D:status>HTTP/1.1 403 Forbidden</D:status>
</D:propstat> </D:propstat>
</D:response> </D:response>
</D:multistatus> </D:multistatus>
9.4.3 Example: Unsuccessful DAV:principal-property-search REPORT 9.4.3 Example: Unsuccessful DAV:principal-property-search REPORT
In this example, the client requests a search on the non-searchable In this example, the client requests a search on the non-searchable
property "phone" in the namespace "http://www.BigCorp.com/ns/". property "phone" in the namespace "http://www.example.com/ns/".
The response is a 403 (Forbidden), with a response body containing The response is a 403 (Forbidden), with a response body containing
Clemm, Hopkins, Sedlar, Whitehead [Page 53]
a DAV:property-must-be-searchable XML element as the value of a a DAV:property-must-be-searchable XML element as the value of a
DAV:error XML element. DAV:error XML element.
>> Request << >> Request <<
REPORT /users/ HTTP/1.1 REPORT /users/ HTTP/1.1
Host: www.BigCorp.com
Clemm, et al. [Page 48]
Host: www.example.com
Content-Type: text/xml; charset=utf-8 Content-Type: text/xml; charset=utf-8
Content-Length: xxxx Content-Length: xxxx
Depth: 0 Depth: 0
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:principal-property-search xmlns:D="DAV:"> <D:principal-property-search xmlns:D="DAV:">
<D:property-search> <D:property-search>
<D:prop xmlns:B="http://www.BigCorp.com/ns/"> <D:prop xmlns:B="http://www.example.com/ns/">
<B:phone/> <B:phone/>
</D:prop> </D:prop>
<D:match>232</D:match> <D:match>232</D:match>
</D:property-search> </D:property-search>
</D:principal-property-search> </D:principal-property-search>
>> Response << >> Response <<
HTTP/1.1 403 Forbidden HTTP/1.1 403 Forbidden
Content-Type: text/xml; charset=utf-8 Content-Type: text/xml; charset=utf-8
Content-Length: xxxx Content-Length: xxxx
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:error xmlns:D="DAV:"> <D:error xmlns:D="DAV:">
<D:property-must-be-searchable> <D:property-must-be-searchable>
<D:prop xmlns:B="http://www.BigCorp.com/ns/"> <D:prop xmlns:B="http://www.example.com/ns/">
<B:phone/> <B:phone/>
</D:prop> </D:prop>
</D:property-must-be-searchable> </D:property-must-be-searchable>
</D:error> </D:error>
9.5 DAV:principal-search-property-set REPORT 9.5 DAV:principal-search-property-set REPORT
The DAV:principal-search-property-set REPORT identifies those The DAV:principal-search-property-set REPORT identifies those
properties that may be searched using the DAV:principal-property- properties that may be searched using the DAV:principal-property-
search REPORT (defined in Section 9.4). search REPORT (defined in Section 9.4).
Servers MUST support the DAV:principal-search-property-set REPORT Servers MUST support the DAV:principal-search-property-set REPORT
on all collections identified in the value of a DAV:principal- on all collections identified in the value of a DAV:principal-
collection-set property. collection-set property.
Clemm, Hopkins, Sedlar, Whitehead [Page 54]
An access control protocol user agent could use the results of the An access control protocol user agent could use the results of the
DAV:principal-search-property-set REPORT to present a query DAV:principal-search-property-set REPORT to present a query
interface to the user for retrieving principals. interface to the user for retrieving principals.
Support for this report is REQUIRED. Support for this report is REQUIRED.
Implementation Note: Some clients will have only limited screen Implementation Note: Some clients will have only limited screen
real estate for the display of lists of searchable properties. real estate for the display of lists of searchable properties. In
In this case, a user might appreciate having the most frequently this case, a user might appreciate having the most frequently
searched properties be displayed on-screen, rather than having searched properties be displayed on-screen, rather than having to
to scroll through a long list of searchable properties. One scroll through a long list of searchable properties. One mechanism
mechanism for signaling the most frequently searched properties
is to return them towards the start of a list of properties. A Clemm, et al. [Page 49]
client can then preferentially display the list of properties in for signaling the most frequently searched properties is to return
order, increasing the likelihood that the most frequently them towards the start of a list of properties. A client can then
searched properties will appear on-screen, and will not require preferentially display the list of properties in order, increasing
scrolling for their selection. the likelihood that the most frequently searched properties will
appear on-screen, and will not require scrolling for their
selection.
Marshalling: Marshalling:
The request body MUST be an empty DAV:principal-search-property-set The request body MUST be an empty DAV:principal-search-property-set
XML element. XML element.
This report is only defined when the Depth header has value "0"; This report is only defined when the Depth header has value "0";
other values result in a 400 (Bad Request) error response. Note other values result in a 400 (Bad Request) error response. Note
that [RFC3253], Section 3.6, states that if the Depth header is not that [RFC3253], Section 3.6, states that if the Depth header is not
present, it defaults to a value of "0". present, it defaults to a value of "0".
The response body MUST be a DAV:principal-search-property-set XML The response body MUST be a DAV:principal-search-property-set XML
element, containing a DAV:principal-search-property XML element for element, containing a DAV:principal-search-property XML element for
skipping to change at line 2657 skipping to change at line 2658
that [RFC3253], Section 3.6, states that if the Depth header is not that [RFC3253], Section 3.6, states that if the Depth header is not
present, it defaults to a value of "0". present, it defaults to a value of "0".
The response body MUST be a DAV:principal-search-property-set XML The response body MUST be a DAV:principal-search-property-set XML
element, containing a DAV:principal-search-property XML element for element, containing a DAV:principal-search-property XML element for
each property that may be searched with the DAV:principal-property- each property that may be searched with the DAV:principal-property-
search REPORT. A server MAY limit its response to just a subset of search REPORT. A server MAY limit its response to just a subset of
the searchable properties, such as those likely to be useful to an the searchable properties, such as those likely to be useful to an
interactive access control client. interactive access control client.
<!ELEMENT principal-search-property-set (principal-search- <!ELEMENT principal-search-property-set (principal-search-property*) >
property*) >
Each DAV:principal-search-property XML element contains exactly one Each DAV:principal-search-property XML element contains exactly one
searchable property, and a description of the property. searchable property, and a description of the property.
<!ELEMENT principal-search-property (prop, description) > <!ELEMENT principal-search-property (prop, description) >
The DAV:prop element contains one principal property on which the The DAV:prop element contains one principal property on which the
server is able to perform a DAV:principal-property-search REPORT. server is able to perform a DAV:principal-property-search REPORT.
prop: see RFC 2518, Section 12.11 prop: see RFC 2518, Section 12.11
Clemm, Hopkins, Sedlar, Whitehead [Page 55]
The description element is a human-readable description of what The description element is a human-readable description of what
information this property represents. Servers MUST indicate the information this property represents. Servers MUST indicate the
human language of the description using the xml:lang attribute and human language of the description using the xml:lang attribute and
SHOULD consider the HTTP Accept-Language request header when SHOULD consider the HTTP Accept-Language request header when
selecting one of multiple available languages. selecting one of multiple available languages.
<!ELEMENT description #PCDATA > <!ELEMENT description #PCDATA >
9.5.1 Example: DAV:principal-search-property-set REPORT 9.5.1 Example: DAV:principal-search-property-set REPORT
In this example, the client determines the set of searchable In this example, the client determines the set of searchable
principal properties by requesting the DAV:principal-search- principal properties by requesting the DAV:principal-search-
property-set REPORT on the root of the server's principal URL property-set REPORT on the root of the server's principal URL
collection set, identified by http://www.BigCorp.com/users/. collection set, identified by http://www.example.com/users/.
>> Request << >> Request <<
Clemm, et al. [Page 50]
REPORT /users/ HTTP/1.1 REPORT /users/ HTTP/1.1
Host: www.BigCorp.com Host: www.example.com
Content-Type: text/xml; charset="utf-8" Content-Type: text/xml; charset="utf-8"
Content-Length: xxx Content-Length: xxx
Accept-Language: en, de Accept-Language: en, de
Authorization: BASIC d2FubmFtYWs6cGFzc3dvcmQ= Authorization: BASIC d2FubmFtYWs6cGFzc3dvcmQ=
Depth: 0 Depth: 0
<?xml version="1.0" encoding="utf-8" ?> <?xml version="1.0" encoding="utf-8" ?>
<D:principal-search-property-set xmlns:D="DAV:"/> <D:principal-search-property-set xmlns:D="DAV:"/>
>> Response << >> Response <<
skipping to change at line 2717 skipping to change at line 2717
<D:principal-search-property> <D:principal-search-property>
<D:prop> <D:prop>
<D:displayname/> <D:displayname/>
</D:prop> </D:prop>
<D:description xml:lang="en">Full name</D:description> <D:description xml:lang="en">Full name</D:description>
</D:principal-search-property> </D:principal-search-property>
<D:principal-search-property> <D:principal-search-property>
<D:prop xmlns:B="http://BigCorp.com/ns/"> <D:prop xmlns:B="http://BigCorp.com/ns/">
<B:title/> <B:title/>
</D:prop> </D:prop>
Clemm, Hopkins, Sedlar, Whitehead [Page 56]
<D:description xml:lang="en">Job title</D:description> <D:description xml:lang="en">Job title</D:description>
</D:principal-search-property> </D:principal-search-property>
</D:principal-search-property-set> </D:principal-search-property-set>
10 XML PROCESSING 10 XML PROCESSING
Implementations of this specification MUST support the XML element Implementations of this specification MUST support the XML element
ignore rule, as specified in Section 23.3.2 of [RFC2518], and the ignore rule, as specified in Section 23.3.2 of [RFC2518], and the
XML Namespacerecommendation [REC-XML-NAMES]. XML Namespacerecommendation [REC-XML-NAMES].
skipping to change at line 2740 skipping to change at line 2738
property names defined in a standards-track or Experimental IETF property names defined in a standards-track or Experimental IETF
RFC. RFC.
11 INTERNATIONALIZATION CONSIDERATIONS 11 INTERNATIONALIZATION CONSIDERATIONS
In this specification, the only human-readable content can be found In this specification, the only human-readable content can be found
in the description XML element, found within the DAV:supported- in the description XML element, found within the DAV:supported-
privilege-set property. This element contains a human-readable privilege-set property. This element contains a human-readable
description of the capabilities controlled by a privilege. As a description of the capabilities controlled by a privilege. As a
result, the description element must be capable of representing result, the description element must be capable of representing
Clemm, et al. [Page 51]
descriptions in multiple character sets. Since the description descriptions in multiple character sets. Since the description
element is found within a WebDAV property, it is represented on- element is found within a WebDAV property, it is represented on the
the-wire as XML [REC-XML], and hence can leverage XML's language wire as XML [REC-XML], and hence can leverage XML's language
tagging and character set encoding capabilities. Specifically, XML tagging and character set encoding capabilities. Specifically, XML
processors must, at minimum, be able to read XML elements encoded processors at minimum must be able to read XML elements encoded
using the UTF-8 [UTF-8] encoding of the ISO 10646 multilingual using the UTF-8 [UTF-8] encoding of the ISO 10646 multilingual
plane. XML examples in this specification demonstrate use of the plane. XML examples in this specification demonstrate use of the
charset parameter of the Content-Type header, as defined in charset parameter of the Content-Type header, as defined in
[RFC3023], as well as the XML "encoding" attribute, which together [RFC3023], as well as the XML "encoding" attribute, which together
provide charset identification information for MIME and XML provide charset identification information for MIME and XML
processors. Futhermore, this specification requires server processors. Futhermore, this specification requires server
implementations to tag description fields with the xml:lang implementations to tag description fields with the xml:lang
attribute (see Section 2.12 of [REC-XML]), which specifies the attribute (see Section 2.12 of [REC-XML]), which specifies the
human language of the description. Additionally, server human language of the description. Additionally, server
implementations should take into account the value of the Accept- implementations should take into account the value of the Accept-
skipping to change at line 2766 skipping to change at line 2766
return. return.
For XML elements other than the description element, it is expected For XML elements other than the description element, it is expected
that implementations will treat the property names, privilege that implementations will treat the property names, privilege
names, and values as tokens, and convert these tokens into human- names, and values as tokens, and convert these tokens into human-
readable text in the user's language and character set when readable text in the user's language and character set when
displayed to a person. Only a generic WebDAV property display displayed to a person. Only a generic WebDAV property display
utility would display these values in their raw form to a human utility would display these values in their raw form to a human
user. user.
Clemm, Hopkins, Sedlar, Whitehead [Page 57]
For error reporting, we follow the convention of HTTP/1.1 status For error reporting, we follow the convention of HTTP/1.1 status
codes, including with each status code a short, English description codes, including with each status code a short, English description
of the code (e.g., 200 (OK)). While the possibility exists that a of the code (e.g., 200 (OK)). While the possibility exists that a
poorly crafted user agent would display this message to a user, poorly crafted user agent would display this message to a user,
internationalized applications will ignore this message, and internationalized applications will ignore this message, and
display an appropriate message in the user's language and character display an appropriate message in the user's language and character
set. set.
Further internationalization considerations for this protocol are Further internationalization considerations for this protocol are
described in the WebDAV Distributed Authoring protocol described in the WebDAV Distributed Authoring protocol
skipping to change at line 2793 skipping to change at line 2792
addition to the discussion in this document, the security addition to the discussion in this document, the security
considerations detailed in the HTTP/1.1 specification [RFC2616], considerations detailed in the HTTP/1.1 specification [RFC2616],
the WebDAV Distributed Authoring Protocol specification [RFC2518], the WebDAV Distributed Authoring Protocol specification [RFC2518],
and the XML Media Types specification [RFC3023] should be and the XML Media Types specification [RFC3023] should be
considered in a security analysis of this protocol. considered in a security analysis of this protocol.
12.1 Increased Risk of Compromised Users 12.1 Increased Risk of Compromised Users
In the absence of a mechanism for remotely manipulating access In the absence of a mechanism for remotely manipulating access
control lists, if a single user's authentication credentials are control lists, if a single user's authentication credentials are
Clemm, et al. [Page 52]
compromised, only those resources for which the user has access compromised, only those resources for which the user has access
permission can be read, modified, moved, or deleted. With the permission can be read, modified, moved, or deleted. With the
introduction of this access control protocol, if a single introduction of this access control protocol, if a single
compromised user has the ability to change ACLs for a broad range compromised user has the ability to change ACLs for a broad range
of other users (e.g., a super-user), the number of resources that of other users (e.g., a super-user), the number of resources that
could be altered by a single compromised user increases. This risk could be altered by a single compromised user increases. This risk
can be mitigated by limiting the number of people who have write- can be mitigated by limiting the number of people who have write-
acl privileges across a broad range of resources. acl privileges across a broad range of resources.
12.2 Risks of the DAV:read-acl and DAV:current-user-privilege-set 12.2Risks of the DAV:read-acl and DAV:current-user-privilege-set Privileges
Privileges
The ability to read the access privileges (stored in the DAV:acl The ability to read the access privileges (stored in the DAV:acl
property), or the privileges permitted the currently authenticated property), or the privileges permitted the currently authenticated
user (stored in the DAV:current-user-privilege-set property) on a user (stored in the DAV:current-user-privilege-set property) on a
resource may seem innocuous, since reading an ACL cannot possibly resource may seem innocuous, since reading an ACL cannot possibly
affect the resource's state. However, if all resources have world- affect the resource's state. However, if all resources have world-
readable ACLs, it is possible to perform an exhaustive search for readable ACLs, it is possible to perform an exhaustive search for
those resources that have inadvertently left themselves in a those resources that have inadvertently left themselves in a
vulnerable state, such as being world-writeable. In particular, the vulnerable state, such as being world-writeable. In particular, the
property retrieval method PROPFIND, executed with Depth infinity on property retrieval method PROPFIND, executed with Depth infinity on
an entire hierarchy, is a very efficient way to retrieve the an entire hierarchy, is a very efficient way to retrieve the
Clemm, Hopkins, Sedlar, Whitehead [Page 58]
DAV:acl or DAV:current-user-privilege-set properties. Once found, DAV:acl or DAV:current-user-privilege-set properties. Once found,
this vulnerability can be exploited by a denial of service attack this vulnerability can be exploited by a denial of service attack
in which the open resource is repeatedly overwritten. Alternately, in which the open resource is repeatedly overwritten. Alternately,
writeable resources can be modified in undesirable ways. writeable resources can be modified in undesirable ways.
To reduce this risk, read-acl privileges should not be granted to To reduce this risk, read-acl privileges should not be granted to
unauthenticated principals, and restrictions on read-acl and read- unauthenticated principals, and restrictions on read-acl and read-
current-user-privilege-set privileges for authenticated principals current-user-privilege-set privileges for authenticated principals
should be carefully analyzed when deploying this protocol. Access should be carefully analyzed when deploying this protocol. Access
to the current-user-privilege-set property will involve a tradeoff to the current-user-privilege-set property will involve a tradeoff
skipping to change at line 2848 skipping to change at line 2846
specification intentionally does not address the issue of how to specification intentionally does not address the issue of how to
manage or discover the initial ACL that is placed upon a resource manage or discover the initial ACL that is placed upon a resource
when it is created. The only way to discover the initial ACL is to when it is created. The only way to discover the initial ACL is to
create a new resource, then retrieve the value of the DAV:acl create a new resource, then retrieve the value of the DAV:acl
property. This assumes the principal creating the resource also has property. This assumes the principal creating the resource also has
been granted the DAV:read-acl privilege. been granted the DAV:read-acl privilege.
As a result, it is possible that a principal could create a As a result, it is possible that a principal could create a
resource, and then discover that its ACL grants privileges that are resource, and then discover that its ACL grants privileges that are
undesirable. Furthermore, this protocol makes it possible (though undesirable. Furthermore, this protocol makes it possible (though
Clemm, et al. [Page 53]
unlikely) that the creating principal could be unable to modify the unlikely) that the creating principal could be unable to modify the
ACL, or even delete the resource. Even when the ACL can be ACL, or even delete the resource. Even when the ACL can be
modified, there will be a short period of time when the resource modified, there will be a short period of time when the resource
exists with the initial ACL before its new ACL can be set. exists with the initial ACL before its new ACL can be set.
Several factors mitigate this risk. Human principals are often Several factors mitigate this risk. Human principals are often
aware of the default access permissions in their editing aware of the default access permissions in their editing
environments and take this into account when writing information. environments and take this into account when writing information.
Furthermore, default privilege policies are usually very Furthermore, default privilege policies are usually very
conservative, limiting the privileges granted by the initial ACL. conservative, limiting the privileges granted by the initial ACL.
13 AUTHENTICATION 13 AUTHENTICATION
Authentication mechanisms defined for use with HTTP and WebDAV also Authentication mechanisms defined for use with HTTP and WebDAV also
apply to this WebDAV Access Control Protocol, in particular the apply to this WebDAV Access Control Protocol, in particular the
Basic and Digest authentication mechanisms defined in [RFC2617]. Basic and Digest authentication mechanisms defined in [RFC2617].
Implementation of the ACL spec requires that Basic authentication,
if used, MUST only be supported over secure transport such as TLS.
Clemm, Hopkins, Sedlar, Whitehead [Page 59]
14 IANA CONSIDERATIONS 14 IANA CONSIDERATIONS
This document uses the namespace defined by [RFC2518] for XML This document uses the namespace defined by [RFC2518] for XML
elements. All other IANA considerations mentioned in [RFC2518] also elements. That is, this specification uses the "DAV:" URI
namespace, previously registered in the URI schemes registry. All
other IANA considerations mentioned in [RFC2518] are also
applicable to this specification. applicable to this specification.
15 INTELLECTUAL PROPERTY 15 INTELLECTUAL PROPERTY
The following notice is copied from RFC 2026, section 10.4, and The following notice is copied from RFC 2026, section 10.4, and
describes the position of the IETF concerning intellectual property describes the position of the IETF concerning intellectual property
claims made against this document. claims made against this document.
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
skipping to change at line 2895 skipping to change at line 2898
standards-related documentation can be found in BCP-11. Copies of standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances claims of rights made available for publication and any assurances
of licenses to be made available, or the result of an attempt made of licenses to be made available, or the result of an attempt made
to obtain a general license or permission for the use of such to obtain a general license or permission for the use of such
proprietary rights by implementers or users of this specification proprietary rights by implementers or users of this specification
can be obtained from the IETF Secretariat. can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to practice rights that may cover technology that may be required to practice
Clemm, et al. [Page 54]
this standard. Please address the information to the IETF this standard. Please address the information to the IETF
Executive Director. Executive Director.
16 ACKNOWLEDGEMENTS 16 ACKNOWLEDGEMENTS
This protocol is the collaborative product of the WebDAV ACL design This protocol is the collaborative product of the WebDAV ACL design
team: Bernard Chester, Geoff Clemm, Anne Hopkins, Barry Lind, Sean team: Bernard Chester, Geoff Clemm, Anne Hopkins, Barry Lind, Sean
Lyndersay, Eric Sedlar, Greg Stein, and Jim Whitehead. The authors Lyndersay, Eric Sedlar, Greg Stein, and Jim Whitehead. The authors
are grateful for the detailed review and comments provided by Jim are grateful for the detailed review and comments provided by Jim
Amsden, Dylan Barrell, Gino Basso, Murthy Chintalapati, Lisa Amsden, Dylan Barrell, Gino Basso, Murthy Chintalapati, Lisa
Dusseault, Stefan Eissing, Tim Ellison, Yaron Goland, Dennis Dusseault, Stefan Eissing, Tim Ellison, Yaron Goland, Dennis
Hamilton, Laurie Harper, Eckehard Hermann, Ron Jacobs, Chris Hamilton, Laurie Harper, Eckehard Hermann, Ron Jacobs, Chris
Knight, Remy Maucherat, Larry Masinter, Joe Orton, Peter Raymond, Knight, Remy Maucherat, Larry Masinter, Joe Orton, Peter Raymond,
Julian Reschke, and Keith Wannamaker. We thank Keith Wannamaker for Julian Reschke, and Keith Wannamaker. We thank Keith Wannamaker for
the initial text of the principal property search sections. Prior the initial text of the principal property search sections. Prior
work on WebDAV access control protocols has been performed by Yaron work on WebDAV access control protocols has been performed by Yaron
Goland, Paul Leach, Lisa Dusseault, Howard Palmer, and Jon Radoff. Goland, Paul Leach, Lisa Dusseault, Howard Palmer, and Jon Radoff.
We would like to acknowledge the foundation laid for us by the We would like to acknowledge the foundation laid for us by the
authors of the DeltaV, WebDAV and HTTP protocols upon which this authors of the DeltaV, WebDAV and HTTP protocols upon which this
Clemm, Hopkins, Sedlar, Whitehead [Page 60]
protocol is layered, and the invaluable feedback from the WebDAV protocol is layered, and the invaluable feedback from the WebDAV
working group. working group.
17 REFERENCES 17 REFERENCES
17.1 Normative References 17.1 Normative References
[RFC2119] S.Bradner, "Key words for use in RFCs to Indicate [RFC2119] S.Bradner, "Key words for use in RFCs to Indicate
Requirement Levels." RFC 2119, BCP 14, March, 1997. Requirement Levels." RFC 2119, BCP 14, March, 1997.
skipping to change at line 2949 skipping to change at line 2952
http://www.w3.org/TR/xml-infoset/ http://www.w3.org/TR/xml-infoset/
[RFC2616] R. Fielding, J. Gettys, J. C. Mogul, H. Frystyk, L. [RFC2616] R. Fielding, J. Gettys, J. C. Mogul, H. Frystyk, L.
Masinter, P. Leach, and T. Berners-Lee, "Hypertext Transfer Masinter, P. Leach, and T. Berners-Lee, "Hypertext Transfer
Protocol -- HTTP/1.1." RFC 2616, June, 1999. Protocol -- HTTP/1.1." RFC 2616, June, 1999.
[RFC2617] J. Franks, P. Hallam-Baker, J. Hostetler, S. Lawrence, P. [RFC2617] J. Franks, P. Hallam-Baker, J. Hostetler, S. Lawrence, P.
Leach, A. Luotonen, L. Stewart, "HTTP Authentication: Basic and Leach, A. Luotonen, L. Stewart, "HTTP Authentication: Basic and
Digest Access Authentication." RFC 2617, June, 1999. Digest Access Authentication." RFC 2617, June, 1999.
Clemm, et al. [Page 55]
[RFC2518] Y. Goland, E. Whitehead, A. Faizi, S. R. Carter, D. [RFC2518] Y. Goland, E. Whitehead, A. Faizi, S. R. Carter, D.
Jensen, "HTTP Extensions for Distributed Authoring -- WEBDAV." RFC Jensen, "HTTP Extensions for Distributed Authoring -- WEBDAV." RFC
2518, February, 1999. 2518, February, 1999.
[RFC2368] P. Hoffman, L. Masinter, J. Zawinski, "The mailto URL [RFC2368] P. Hoffman, L. Masinter, J. Zawinski, "The mailto URL
scheme." RFC 2368, July, 1998. scheme." RFC 2368, July, 1998.
[RFC3023] M. Murata, S. St.Laurent, D. Kohn, "XML Media Types." RFC [RFC3023] M. Murata, S. St.Laurent, D. Kohn, "XML Media Types." RFC
3023, January, 2001. 3023, January, 2001.
[RFC3010] S. Shepler, B. Callaghan, D. Robinson, R. Thurlow, C.
Beame, M. Eisler, D.Noveck "NFS version 4 Protocol." RFC 3010,
December 2000.
[UTF-8] F. Yergeau, "UTF-8, a transformation format of Unicode and [UTF-8] F. Yergeau, "UTF-8, a transformation format of Unicode and
ISO 10646." RFC 2279, January, 1998. ISO 10646." RFC 2279, January, 1998.
17.2 Informational References 17.2 Informational References
[RFC2026] S.Bradner, "The Internet Standards Process - Revision 3." [RFC2026] S.Bradner, "The Internet Standards Process - Revision 3."
RFC 2026, BCP 9. Harvard, October, 1996. RFC 2026, BCP 9. Harvard, October, 1996.
Clemm, Hopkins, Sedlar, Whitehead [Page 61]
[RFC2255] T. Howes, M. Smith, "The LDAP URL Format." RFC 2255. [RFC2255] T. Howes, M. Smith, "The LDAP URL Format." RFC 2255.
Netscape, December, 1997. Netscape, December, 1997.
[RFC2251] M. Wahl, T. Howes, S. Kille, "Lightweight Directory [RFC2251] M. Wahl, T. Howes, S. Kille, "Lightweight Directory
Access Protocol (v3)." RFC 2251. Critical Angle, Netscape, Isode, Access Protocol (v3)." RFC 2251. Critical Angle, Netscape, Isode,
December, 1997. December, 1997.
[CaseMap] M. Davis, "Case Mappings", Unicode Standard Annex #21, [CaseMap] M. Davis, "Case Mappings", Unicode Standard Annex #21,
March 26, 2001. http://www.unicode.org/unicode/reports/tr21 March 26, 2001. http://www.unicode.org/unicode/reports/tr21
Clemm, et al. [Page 56]
18 AUTHORS' ADDRESSES 18 AUTHORS' ADDRESSES
Geoffrey Clemm Geoffrey Clemm
Rational Software
IBM
20 Maguire Road 20 Maguire Road
Lexington, MA 02421 Lexington, MA 02421
Email: geoffrey.clemm@rational.com
Email: geoffrey.clemm@us.ibm.com
Anne Hopkins Anne Hopkins
Microsoft Corporation Microsoft Corporation
One Microsoft Way One Microsoft Way
Redmond, WA 98052 Redmond, WA 98052
Email: annehop@microsoft.com Email: annehop@microsoft.com
Eric Sedlar Eric Sedlar
Oracle Corporation Oracle Corporation
500 Oracle Parkway 500 Oracle Parkway
Redwood Shores, CA 94065 Redwood Shores, CA 94065
Email: esedlar@us.oracle.com
Email: eric.sedlar@oracle.com
Jim Whitehead Jim Whitehead
U.C. Santa Cruz U.C. Santa Cruz
Dept. of Computer Science Dept. of Computer Science
Baskin Engineering Baskin Engineering
1156 High Street 1156 High Street
Santa Cruz, CA 95064 Santa Cruz, CA 95064
Email: ejw@cse.ucsc.edu Email: ejw@cse.ucsc.edu
Clemm, Hopkins, Sedlar, Whitehead [Page 62] Clemm, et al. [Page 57]
19 APPENDICES 19 APPENDICES
19.1 WebDAV XML Document Type Definition Addendum 19.1 WebDAV XML Document Type Definition Addendum
All XML elements defined in this Document Type Definition (DTD) All XML elements defined in this Document Type Definition (DTD)
belong to the DAV namespace. This DTD should be viewed as an belong to the DAV namespace. This DTD should be viewed as an
addendum to the DTD provided in [RFC2518], section 23.1. addendum to the DTD provided in [RFC2518], section 23.1.
<!-- Privileges --> <!-- Privileges -->
skipping to change at line 3054 skipping to change at line 3074
<!ELEMENT supported-privilege-set (supported-privilege*)> <!ELEMENT supported-privilege-set (supported-privilege*)>
<!ELEMENT supported-privilege <!ELEMENT supported-privilege
(privilege, abstract?, description, supported-privilege*)> (privilege, abstract?, description, supported-privilege*)>
<!ELEMENT privilege ANY> <!ELEMENT privilege ANY>
<!ELEMENT abstract EMPTY> <!ELEMENT abstract EMPTY>
<!ELEMENT description #PCDATA> <!ELEMENT description #PCDATA>
<!ELEMENT privilege ANY> <!ELEMENT privilege ANY>
Clemm, Hopkins, Sedlar, Whitehead [Page 63]
<!-- DAV:current-user-privilege-set Property (Section 5.3) --> <!-- DAV:current-user-privilege-set Property (Section 5.3) -->
Clemm, et al. [Page 58]
<!ELEMENT current-user-privilege-set (privilege*)> <!ELEMENT current-user-privilege-set (privilege*)>
<!-- DAV:acl Property (Section 5.4) --> <!-- DAV:acl Property (Section 5.4) -->
<!ELEMENT acl (ace)* > <!ELEMENT acl (ace)* >
<!ELEMENT ace (invert | principal, (grant|deny), protected?, <!ELEMENT ace (invert | principal, (grant|deny), protected?, inherited?)>
inherited?)>
<!ELEMENT invert principal> <!ELEMENT invert principal>
<!ELEMENT principal ((href, prop?) <!ELEMENT principal ((href, prop?)
| all | authenticated | unauthenticated | all | authenticated | unauthenticated
| property | self)> | property | self)>
<!ELEMENT prop (see [RFC2518], section 12.11)> <!ELEMENT prop (see [RFC2518], section 12.11)>
<!ELEMENT all EMPTY> <!ELEMENT all EMPTY>
<!ELEMENT authenticated EMPTY> <!ELEMENT authenticated EMPTY>
<!ELEMENT unauthenticated EMPTY> <!ELEMENT unauthenticated EMPTY>
skipping to change at line 3095 skipping to change at line 3114
<!-- DAV:inherited-acl-set Property (Section 5.6) --> <!-- DAV:inherited-acl-set Property (Section 5.6) -->
<!ELEMENT inherited-acl-set (href*)> <!ELEMENT inherited-acl-set (href*)>
<!-- DAV:principal-collection-set Property (Section 5.6) --> <!-- DAV:principal-collection-set Property (Section 5.6) -->
<!ELEMENT principal-collection-set (href*)> <!ELEMENT principal-collection-set (href*)>
<!-- DAV:acl-semantics Property (Section 6) --> <!-- DAV:acl-semantics Property (Section 6) -->
<!ELEMENT acl-semantics (ace-combination?, ace-ordering?, allowed- <!ELEMENT acl-semantics (ace-combination?, ace-ordering?, allowed-ace?,
ace?, required-principal?)> required-principal?)>
Clemm, Hopkins, Sedlar, Whitehead [Page 64]
<!ELEMENT ace-combination <!ELEMENT ace-combination
(first-match | all-grant-before-any-deny | specific-deny- (first-match | all-grant-before-any-deny | specific-deny-overrides-grant)>
overrides-grant)>
<!ELEMENT first-match EMPTY> <!ELEMENT first-match EMPTY>
<!ELEMENT all-grant-before-any-deny EMPTY> <!ELEMENT all-grant-before-any-deny EMPTY>
<!ELEMENT specific-deny-overrides-grant EMPTY> <!ELEMENT specific-deny-overrides-grant EMPTY>
<!ELEMENT ace-ordering (deny-before-grant)? > <!ELEMENT ace-ordering (deny-before-grant)? >
<!ELEMENT deny-before-grant EMPTY> <!ELEMENT deny-before-grant EMPTY>
<!ELEMENT allowed-ace (principal-only-one-ace | grant-only | <!ELEMENT allowed-ace (grant-only |
no-invert | no-acl-inherit)*>
<!ELEMENT principal-only-one-ace EMPTY> Clemm, et al. [Page 59]
no-invert)*>
<!ELEMENT grant-only EMPTY> <!ELEMENT grant-only EMPTY>
<!ELEMENT no-invert EMPTY> <!ELEMENT no-invert EMPTY>
<!ELEMENT no-acl-inherit EMPTY>
<!ELEMENT required-principal <!ELEMENT required-principal
(all? | authenticated? | unauthenticated? | self? | href* (all? | authenticated? | unauthenticated? | self? | href* |property*)>
|property*)>
<!-- ACL method preconditions (Section 8.1.1) --> <!-- ACL method preconditions (Section 8.1.1) -->
<!ELEMENT no-ace-conflict EMPTY> <!ELEMENT no-ace-conflict EMPTY>
<!ELEMENT no-protected-ace-conflict EMPTY> <!ELEMENT no-protected-ace-conflict EMPTY>
<!ELEMENT no-inherited-ace-conflict EMPTY> <!ELEMENT no-inherited-ace-conflict EMPTY>
<!ELEMENT limited-number-of-aces EMPTY> <!ELEMENT limited-number-of-aces EMPTY>
<!ELEMENT no-abstract EMPTY> <!ELEMENT no-abstract EMPTY>
<!ELEMENT not-supported-privilege EMPTY> <!ELEMENT not-supported-privilege EMPTY>
<!ELEMENT missing-required-principal EMPTY> <!ELEMENT missing-required-principal EMPTY>
<!ELEMENT recognized-principal EMPTY> <!ELEMENT recognized-principal EMPTY>
<!ELEMENT allowed-principal EMPTY> <!ELEMENT allowed-principal EMPTY>
<!-- REPORTs (Section 9) --> <!-- REPORTs (Section 9) -->
<!ELEMENT acl-principal-prop-set ANY> <!ELEMENT acl-principal-prop-set ANY>
ANY value: a sequence of one or more elements, with at most one ANY value: a sequence of one or more elements, with at most one DAV:prop
DAV:prop element. element.
<!ELEMENT principal-match ((principal-property | self), prop?)> <!ELEMENT principal-match ((principal-property | self), prop?)>
<!ELEMENT principal-property ANY> <!ELEMENT principal-property ANY>
ANY value: an element whose value identifies a property. The ANY value: an element whose value identifies a property. The expectation is
expectation is the value of the named property typically contains the value of the named property typically contains an href element that
an href element that contains the URI of a principal contains the URI of a principal
Clemm, Hopkins, Sedlar, Whitehead [Page 65]
<!ELEMENT self EMPTY> <!ELEMENT self EMPTY>
<!ELEMENT principal-property-search ((property-search+), prop?) > <!ELEMENT principal-property-search ((property-search+), prop?) >
<!ELEMENT property-search (prop, match) > <!ELEMENT property-search (prop, match) >
<!ELEMENT match #PCDATA > <!ELEMENT match #PCDATA >
<!ELEMENT principal-search-property-set (principal-search- <!ELEMENT principal-search-property-set (principal-search-property*) >
property*) >
<!ELEMENT principal-search-property (prop, description) > <!ELEMENT principal-search-property (prop, description) >
Clemm, Hopkins, Sedlar, Whitehead [Page 66] 19.2WebDAV Method Privilege Table (Normative)
The following table of WebDAV methods (as defined in RFC 2518, 2616, and
3253) clarifies which privileges are required for access for each
method. Note that the privileges listed, if denied, MUST cause access
to be denied. However, given that a specific implementation MAY define
an additional custom privilege to control access to existing methods,
having all of the indicated privileges does not mean that access will be
granted. Note that lack of the indicated privileges does not imply that
access will be denied, since a particular implementation may use a sub-
privilege aggregated under the indicated privilege to control access.
Clemm, et al. [Page 60]
Privileges required refer to the current resource being processed unless
otherwise specified.
METHOD PRIVILEGES
GET <D:read>
HEAD <D:read>
OPTIONS <D:read>
PUT <D:write-content> (on parent coll if resource
doesn't already exist, or on existing resource
otherwise)
PROPPATCH <D:write-properties>
ACL <D:write-acl>
PROPFIND <D:read> (plus <read-acl> and
<read-current-user-privilege-set> as needed)
COPY <D:read>, <D:write-content> on target collection
MOVE (no target exists) <D:write-content> on source&target coll, plus
<dav:read>
on the resource being moved MAY be required
MOVE (target exists) As above, plus <D:delete> on the resource to be
overwritten
DELETE <D:delete>, <D:write-content> on parent collection
LOCK <D:write-content>
MKCOL <D:write-content> (on parent coll)
UNLOCK <D:unlock>
CHECKOUT <D:write>
CHECKIN <D:write>
REPORT <D:read> (on all referenced resources)
VERSION-CONTROL <D:write>
MERGE <D:write-content>
MKWORKSPACE <D:write-content> on parent collection
BASELINE-CONTROL <D:write>
MKACTIVITY <D:write-content> on parent collection
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/