Difference between revisions of "AccessControl"

From Linked Data Platform
Jump to: navigation, search
(Requirements)
(Requirements)
Line 45: Line 45:
 
* Ability to explain access control policies. (Usecases 5,6)
 
* Ability to explain access control policies. (Usecases 5,6)
 
The ability for a user to query the ACGs that apply to her.
 
The ability for a user to query the ACGs that apply to her.
 +
 +
== Outline of a Charter for a Access Control WG ==
 +
 +
An Access Control Graph (ACG) consists of two kinds of collections: a collection of agents and a collection of resources.  It then connects a collection of agents with a collection of resources with the connection identifying the privileges the agents have on the resources: CREATE, READ, UPDATE,  DELETE.
 +
 +
The members of the collection of agents contain tokens that the agents obtain from some authentication service.  The members of the collection of resources are URIs or URI templates.
 +
 +
=== Deliverables ===
 +
 +
Define the collections that are part of the ACG and define how a collection of agents is connected to a connection of resources.
 +
 +
Describe how a request for access to a resource by an agent can be processed efficiently with the ACG structure defined above.

Revision as of 11:54, 13 May 2014

This page includes content for a note on Use Cases and Requirements for Access Control to be produced by the Linked Data Platform WG. It also outlines a charter for developing a standard for HTTP-based access control. The work discussed in the charter may be pursued in the Linked Data Platform WG or an independent, related WG.

Earlier thinking about Access Control has been moved to Old Access Control Page.


1 Access Control

Access Control is a mechanism through which permissions are granted (or denied) to entities -- individuals, organizations, and/or groups made up of these -- to perform operations on resources. Within this document, the resources are LDP resources, but the access control may operate at different granularities: RDF or other documents, named graphs, individual triples, or individual attributes. The operations are create, read, update, and delete (CRUD).

When an entity requests a collection of resources it gets to see only those resources or parts of resources it is authorized for.

Depending on the granularity, the access control mechanisms may affect performance, but should not affect semantics.

For access control to come into play, the server must restrict some operations on some resources.

2 Vocabulary

  • ACG: An Access Control Graph describes which agents can have some mode of access to a resource, or collection of resources.
  • ACG Resource: A resource whose representation contains one or more ACGs and which the server relies upon to make its access control decisions.

3 Usecases

  1. Adam logs on to a server and requests:
    1. the ability to READ, UPDATE, CREATE or DELETE a resource identified by a URL. The server allows or denies the request as specified the by the ACG for the resource.
    2. the ability to UPDATE, CREATE or DELETE an attribute of the resource identified by the URL. The server allows or denies the request as specified the by the ACG for the resource and attribute and whether fine-grained access control is supported.
  2. Bart logs on to a server and requests:
    1. the ability to read a group of related resources such as all the papers presented at a conference.
    2. the ability to update an attribute of related resources, for example, to add a copyright notice to each resource.
  3. Employees with job titles VP or SVP can sign (update) supplier contracts.
  4. Charlie, the Webmaster, would like to grant read access to the papers presented at a conference to all the people who attended the conference.
  5. David was denied access to some of the resources or parts of resources he requested. He would like an explanation for why all or part of his request was denied.
  6. Eddie would like to understand the access policy of the server.

4 Requirements

  • User must be able to authenticate herself to a server. After authentication user is handed a userId. (Usecase 1 and others.)
  • Ability to create a collection of userIds -- URIs or URI patterns -- (Usecase 3,4.)
  • Ability to create a collection of resource names -- URIs or URI patterns -- with a specified access policy. (Usecase 2.)
  • Ability to connect a collection of userIds with a collection of resource names with given access privileges. (1,2,3,4)

The above three requirements require the ability, by an authorized agent to CREATE, EDIT, UPDATE relevant ACGs.

  • Ability to specify access privileges at a fine-grained level. (Usecase 2.2)

The above requirement requires the ability, by an authorized agent to CREATE, EDIT, UPDATE relevant ACGs at a fine-grained level.

  • Ability to explain access control policies. (Usecases 5,6)

The ability for a user to query the ACGs that apply to her.

5 Outline of a Charter for a Access Control WG

An Access Control Graph (ACG) consists of two kinds of collections: a collection of agents and a collection of resources. It then connects a collection of agents with a collection of resources with the connection identifying the privileges the agents have on the resources: CREATE, READ, UPDATE, DELETE.

The members of the collection of agents contain tokens that the agents obtain from some authentication service. The members of the collection of resources are URIs or URI templates.

5.1 Deliverables

Define the collections that are part of the ACG and define how a collection of agents is connected to a connection of resources.

Describe how a request for access to a resource by an agent can be processed efficiently with the ACG structure defined above.