Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -2,34 +2,40 @@
2	2	(((
3	3	(% class="container" %)
4	4	(((
5		-= My Collab's Extended Title =
	5	+= Data Proxy =
6	6
7		-My collab's subtitle
	7	+Documentation
8	8	)))
9	9	)))
10	10
11	11	(% class="row" %)
12	12	(((
13		-(% class="col-xs-12 col-sm-8" %)
	13	+(% class="col-xs-12 col-sm-4" %)
14	14	(((
15		-= What can I find here? =
	15	+The data proxy core is the application that acts as a proxy to the CSCS Swift storage.
16	16
17		-* Notice how the table of contents on the right
18		-* is automatically updated
19		-* to hold this page's headers
	17	+==== Authentication ====
20	20
21		-= Who has access? =
	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
22	22
23		-Describe the audience of this collab.
24		-)))
	21	+=== Bucket system ===
25	25
	23	+We use the collaboratory authorization system for the buckets.
26	26
27		-(% class="col-xs-12 col-sm-4" %)
28		-(((
29		-{{box title="**Contents**"}}
30		-{{toc/}}
31		-{{/box}}
	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
32	32
	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	+
33	33
34	34	)))
35	35	)))