Wiki source code of Data Proxy
Version 7.1 by alexisdurieux on 2021/01/06 11:34
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | (% class="jumbotron" %) | ||
| 2 | ((( | ||
| 3 | (% class="container" %) | ||
| 4 | ((( | ||
| 5 | = Data Proxy = | ||
| 6 | |||
| 7 | Documentation | ||
| 8 | ))) | ||
| 9 | ))) | ||
| 10 | |||
| 11 | (% class="row" %) | ||
| 12 | ((( | ||
| 13 | (% class="col-xs-12 col-sm-4" %) | ||
| 14 | ((( | ||
| 15 | The data proxy core is the application that acts as a proxy to the CSCS Swift storage. | ||
| 16 | |||
| 17 | ==== Authentication ==== | ||
| 18 | |||
| 19 | The application itself is connected to the CSCS storage. The user is authenticated against the data-proxy application using an authorization headers. The user is then authenticated against the EBRAINS platform. That means the user only needs to have a ebrains account to access the data proxy and the swift storage capabilities | ||
| 20 | |||
| 21 | === Bucket system === | ||
| 22 | |||
| 23 | We use the collaboratory authorization system for the buckets. | ||
| 24 | |||
| 25 | For every collab, it is possible to access a swift container as a user. The action the user can perform on the buckets depend on the rights the user has in the collab | ||
| 26 | |||
| 27 | (% border="3" %) | ||
| 28 | |=Collab Right|=Available actions on bucket | ||
| 29 | |Viewer|Read | ||
| 30 | |Editor|Create, Read, Update, Delete | ||
| 31 | |Admin|Create, Read, Update, Delete | ||
| 32 | |Not a collab member|No actions | ||
| 33 | |||
| 34 | **Should the editor be able to create the bucket in the first place ?** | ||
| 35 | |||
| 36 | |||
| 37 | === **Api description** === | ||
| 38 | |||
| 39 | |||
| 40 | ))) | ||
| 41 | ))) |