Andreas Jaeger 2d44b2b36d Prepare for Sphinx 1.5

The new sphinx version introduces some changes that break build:

* Warns if code cannot be parsed for highlighting. Fix the code so
  that it can be parsed, this includes uncommenting "..." lines.
  Note that not every config file is an ini-file.
  Also, the parser seems to have bugs and cannot parse all files.
  Fix mysql ini file and enable the parameter, see
http://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_file_per_table
* :option: works only with declared options, replace useage with
  simple ``.

This change only handles a few files, more to come later.

Change-Id: I7c7335e514581622dd562ee355f62d6ae1beaa18

2017-01-11 20:37:55 +01:00

2.6 KiB

Raw Blame History

Manage access

Users have roles on accounts. For example, a user with the admin role has full access to all containers and objects in an account. You can set access control lists (ACLs) at the container level and support lists for read and write access, which you set with the X-Container-Read and X-Container-Write headers.

To give a user read access, use the swift post command with the -r parameter. To give a user write access, use the -w parameter.
The following are examples of read ACLs for containers:

A request with any HTTP referer header can read container contents:
```
$ swift post CONTAINER -r ".r:*"
```
A request with any HTTP referer header can read and list container contents:
```
$ swift post CONTAINER -r ".r:*,.rlistings"
```
A list of specific HTTP referer headers permitted to read container contents:
```
$ swift post CONTAINER -r \
  ".r:openstack.example.com,.r:swift.example.com,.r:storage.example.com"
```
A list of specific HTTP referer headers denied read access:
```
$ swift post CONTAINER -r \
  ".r:*,.r:-openstack.example.com,.r:-swift.example.com,.r:-storage.example.com"
```
All users residing in project1 can read container contents:
```
$ swift post CONTAINER -r "project1:*"
```
User1 from project1 can read container contents:
```
$ swift post CONTAINER -r "project1:user1"
```
A list of specific users and projects permitted to read container contents:
```
$ swift post CONTAINER -r \
  "project1:user1,project1:user2,project3:*,project4:user1"
```
The following are examples of write ACLs for containers:

All users residing in project1 can write to the container:
```
$ swift post CONTAINER -w "project1:*"
```
User1 from project1 can write to the container:
```
$ swift post CONTAINER -w "project1:user1"
```
A list of specific users and projects permitted to write to the container:
```
$ swift post CONTAINER -w \
  "project1:user1,project1:user2,project3:*,project4:user1"
```

Note

To successfully write to a container, a user must have read privileges (in addition to write) on the container. For all aforementioned read/write ACL examples, one can replace the project/user name with project/user UUID, i.e. <project_uuid>:<user_uuid>. If using multiple keystone domains, UUID format is required.

2.6 KiB Raw Blame History

Manage access

2.6 KiB

Raw Blame History