Last modified by alexisdurieux on 2022/03/25 08:38
From version 11.1
edited by alexisdurieux
on 2021/03/30 17:24
Change comment: There is no comment for this version
To version 7.1
edited by alexisdurieux
on 2021/01/06 11:34
Change comment: Uploaded new attachment "Screenshot_2021-01-06 FastAPI - Swagger UI.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -2,10 +2,8 @@
2 2  (((
3 3  (% class="container" %)
4 4  (((
5 -(% style="text-align: justify;" %)
6 6  = Data Proxy =
7 7  
8 -(% style="text-align: justify;" %)
9 9  Documentation
10 10  )))
11 11  )))
... ... @@ -12,34 +12,32 @@
12 12  
13 13  (% class="row" %)
14 14  (((
13 +(% class="col-xs-12 col-sm-4" %)
15 15  (((
16 -(% style="text-align: justify;" %)
17 17  The data proxy core is the application that acts as a proxy to the CSCS Swift storage.
18 18  
19 -(% style="text-align: justify;" %)
20 20  ==== Authentication ====
21 21  
22 -(% style="text-align: justify;" %)
23 -The application itself is connected to the CSCS storage. The user is authenticated against the data-proxy application using authorization headers. The user is then authenticated against the EBRAINS platform. That means the user only needs to have an EBRAINS account to access the data proxy and the Swift storage capabilities
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
24 24  
25 -(% style="text-align: justify;" %)
26 26  === Bucket system ===
27 27  
28 -(% style="text-align: justify;" %)
29 -We use the Collaboratory authorization system for the buckets.
23 +We use the collaboratory authorization system for the buckets.
30 30  
31 -(% style="text-align: justify;" %)
32 -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
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
33 33  
34 34  (% border="3" %)
35 -|=(% style="text-align: justify;" %)Collab Right|=(% style="text-align: justify;" %)Available actions on bucket
36 -|(% style="text-align:justify" %)Viewer|(% style="text-align:justify" %)Read
37 -|(% style="text-align:justify" %)Editor|(% style="text-align:justify" %)Create, Read, Update, Delete
38 -|(% style="text-align:justify" %)Admin|(% style="text-align:justify" %)Create, Read, Update, Delete
39 -|(% style="text-align:justify" %)Not a collab member|(% style="text-align:justify" %)No actions
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
40 40  
41 - 
42 -)))
34 +**Should the editor be able to create the bucket in the first place ?**
43 43  
36 +
37 +=== **Api description** ===
38 +
44 44  
45 45  )))
41 +)))