You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/automate/cmemc-command-line-interface/configuration/certificate-handling-and-ssl-verification/index.md
Copy file name to clipboardExpand all lines: docs/deploy-and-configure/configuration/access-conditions/index.md
+88-63Lines changed: 88 additions & 63 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,13 @@ In order to understand the different user interfaces to manage access conditions
22
22
The following list describes the different attributes, a single access condition can have.
23
23
They are all optional except that a single access condition needs to provide at least one grant or has a dynamic access condition query.
24
24
25
+
The listed IRIs in this section use the following prefix declarations:
26
+
27
+
```turtle
28
+
PREFIX eccauth: <https://vocab.eccenca.com/auth/>
29
+
PREFIX : <https://vocab.eccenca.com/auth/Action/>
30
+
```
31
+
25
32
### **Metadata**
26
33
27
34
-**Name** is a short and human readable text you can give to your access condition in order to identify them.
@@ -36,15 +43,15 @@ They are all optional except that a single access condition needs to provide at
36
43
37
44
| Resource | Explanation |
38
45
| ---------| ------------|
39
-
|`urn:elds-backend-anonymous-user`| Represents the anonymous user account. You can use it in the **Requires account** field. |
46
+
|`eccauth:AnonymousUser`| Represents the anonymous user account. You can use it in the **Requires account** field. |
40
47
41
48
- Use **Requires group** to specify the group, the account must be member of in order to match the access condition.
42
49
If the account of a given request is member of this group, this access condition is used to identify the grants for this request.
43
50
Instead of an actual group, the following meta group can be used.
44
51
45
52
| Resource | Explanation |
46
53
| ---------| ------------|
47
-
|`urn:elds-backend-public-group`| Represents the group which every user is member of (incl. anonymous users). You can use it in the *Requires group* field. |
54
+
|`eccauth:PublicGroup`| Represents the group which every user is member of (incl. anonymous users). You can use it in the *Requires group* field. |
48
55
49
56
!!! warning "Users and groups cannot have the same name"
50
57
@@ -57,28 +64,33 @@ They are all optional except that a single access condition needs to provide at
57
64
58
65
| Resource | Explanation |
59
66
| ---------| ------------|
60
-
|`urn:elds-backend-all-graphs`| Represents all RDF named graphs. You can use it in the *Allow reading graph* or *Allow writing graph* field.|
67
+
|`eccauth:AllGraphs`| Represents all RDF named graphs. You can use it in the *Allow reading graph* or *Allow writing graph* field.|
61
68
62
69
-**Allow writing graph** is a list of graph IRIs to allow to write these graphs.
63
70
The grant to write to a graph implicitly grants to read the graph.
64
71
Instead of an actual graph, the following meta graph can be used.
65
72
66
73
| Resource | Explanation |
67
74
| ---------| ------------|
68
-
|`urn:elds-backend-all-graphs`| Represents all RDF named graphs. You can use it in the *Allow reading graph* or *Allow writing graph* field.|
75
+
|`eccauth:AllGraphs`| Represents all RDF named graphs. You can use it in the *Allow reading graph* or *Allow writing graph* field.|
69
76
70
77
-**Allowed action** is a list of action IRI to allow to use the components or capabilities which are identified with this action.
71
78
You can use the following actions identifier with this attribute.
72
79
73
80
| Resource | Explanation |
74
81
| ---------| ------------|
75
-
|`urn:elds-backend-actions-auth-access-control`| Represents the Authorization Management API (see the Developer Manual).|
76
-
|`urn:eccenca:di`| Represents the action needed to use the eccenca DataIntegration component of eccenca Corporate Memory.|
77
-
|`urn:eccenca:ThesaurusUserInterface`| Represents the action needed to use the Thesaurus Catalog as well as Thesaurus Project editing interface (needs access to specific thesaurus graphs as well).|
78
-
|`urn:eccenca:AccessInternalGraphs`| Represents the action needed to list Corporate Memory Internal graphs in the exploration tab.|
79
-
|`urn:eccenca:QueryUserInterface`| Represents the action needed to use the Query Catalog (needs access to query catalog graph as well).|
80
-
|`urn:eccenca:VocabularyUserInterface`| Represents the action needed to use the Vocabulary Catalog (needs access to specific vocabulary graphs as well).|
81
-
|`urn:eccenca:ExploreUserInterface`| Represents the action needed to use the Explore Tab (needs access to shape catalog graph as well).|
82
+
|`:AllActions`| Represents all actions. You can use it to grant execution rights to all actions |
83
+
|`:Build`| Represents the action needed to use eccenca DataIntegration component of eccenca Corporate Memory. |
84
+
|`:Build-AdminPython`| Represents the action needed to use eccenca DataIntegration's Python plugin management component of eccenca Corporate Memory. |
85
+
|`:Build-AdminWorkspace`| Represents the action needed to use eccenca DataIntegration's workspace administration component of eccenca Corporate Memory. |
86
+
|`:ChangeAccessConditions`| Represents the action needed to use the Authorization management API (see Developer Manual). You can use it as object of the `eccauth:allowedAction` property to grant access to the Authorization management API if the user fulfills the access condition. |
87
+
|`:Explore-BKE-Manage`| Represents the action needed to view, create, edit and delete visualisations in the BKE-Module (needs access to config graph as well). |
88
+
|`:Explore-BKE-Read`| Allows to use the BKE-Module interface in read-only mode (needs access to config graph as well). |
89
+
|`:Explore-KnowledgeGraphs`| Represents the action needed to use the Explore Tab (needs access to at least one graph as well) |
90
+
|`:Explore-ListSystemGraphs`| Represents the action needed to list Corporate Memory system graphs (tagged with shui:isSystemResource) in the Knowledge Graph list. |
91
+
|`:Explore-QueryCatalog`| Represents the action needed to use the Query Catalog (needs access to catalog graph as well if changes should be allowed) |
92
+
|`:Explore-ThesaurusCatalog`| Represents the action needed to use the Thesaurus Catalog as well as Thesaurus Project editing interface (needs access to specific thesaurus graphs as well) |
93
+
|`:Explore-VocabularyCatalog`| Represents the action needed to use the Vocabulary Catalog (needs access to specific vocabulary graphs as well) |
82
94
83
95
In addition to these attributes, you can use the following special attributes to grant partial access to the access conditions itself:
84
96
@@ -138,7 +150,7 @@ The access control module can be selected in the **Admin** section of the left m
138
150
After clicking it, you will see a screen similar to this:
139
151
140
152
<figuremarkdown>
141
-

153
+

142
154
<figcaption>Access Control: List Access Conditions</figcaption>
143
155
</figure>
144
156
@@ -165,7 +177,7 @@ In order to see the rights select a user and / or group combination from the dro
-[`admin user`](../../../automate/cmemc-command-line-interface/command-reference/admin/user/index.md) - List, create, delete and modify user accounts.
192
204
-[`admin client`](../../../automate/cmemc-command-line-interface/command-reference/admin/client/index.md) - List client accounts, get or generate client account secrets.
193
205
194
206
The following session demonstrates how to create a new user, set a password and grant access to certain areas.
0 commit comments