Changes for page Permissions Configuration
Last modified by colinw on 2021/09/10 23:34
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,19 +1,30 @@ 1 +{{layout}} 2 +{{layout-section ac:type="two_right_sidebar"}} 3 +{{layout-cell}} 1 1 {{warning}} 2 2 This page is currently being written. Although the information below is probably accurate, it may not be complete or may have errors. 3 3 {{/warning}} 4 4 5 - 8 +{{info}} 9 +The information on this page applies to **iSymphony 3.1+**. 10 +{{/info}} 6 6 7 -= ===**//Onthispage~://**====12 += (% style="color: rgb(0,0,0);" %)Description(%%) = 8 8 14 +The Permissions resource provides access to query and define permissions for iSymphony. See the reference information below for details about the REST interactions used to define permissions. The rest of this description is provided to make it easier to understand the various interactions that go into the permission system in iSymphony. 15 +{{/layout-cell}} 9 9 17 +{{layout-cell}} 18 +{{panel title="On this page:"}} 10 10 11 -{{toc maxLevel="2" indent="1"/}} 12 12 13 -= Description = 21 +{{toc maxLevel="2" indent="1"/}} 22 +{{/panel}} 23 +{{/layout-cell}} 24 +{{/layout-section}} 14 14 15 - The Permissions resource providesaccess to queryand define permissions for iSymphony. See the reference information below for details aboutthe REST interactionsused to define permissions. The rest of this descriptionis provided to make it easier to understand the various interactions that go into thepermissionsystem in iSymphony.16 - 26 +{{layout-section ac:type="single"}} 27 +{{layout-cell}} 17 17 === Overview === 18 18 19 19 In version 3.0 and previous of iSymphony, permissions were defined for 'permissible' objects in the system - each object that could be controlled via permissions (extensions, queues, other users, etc) would store a list of the users allowed to perform actions on it, and which actions each was allowed to perform. Beginning in version 3.1 of iSymphony, the situation has been reversed, to make it easier to administer permissions and hopefully less confusing. Permissions are defined for each user or user group in the system, in a cascading manner. They are evaluated in order of decreasing specificity, and in the case of a conflicting tie, the action is allowed. This must be considered when using the REST system to define permissions. See the documentation for permissions for more details. ... ... @@ -20,21 +20,35 @@ 20 20 21 21 === Defaults === 22 22 23 -By default, all users in the system are allowed to perform all actions. Therefore, if a specific permission key has not been defined for a user (either on the user itself, or one of the groups it is a member of), that action should be considered allowed. When defining a permission, the default policy is also allowed, unless the allowed 34 +By default, all users in the system are allowed to perform all actions. Therefore, if a specific permission key has not been defined for a user (either on the user itself, or one of the groups it is a member of), that action should be considered allowed. When defining a permission, the default policy is also allowed, unless the allowed flag is set to false. 24 24 25 25 === **Exceptions** === 26 26 27 -The heart of the permission system lies in the exceptions to the rules. This allows for powerful combinations to be achieved. Generally, the objects defined by their UUIDs in the exceptions There are a few special cases.38 +The heart of the permission system lies in the exceptions to the rules. This allows for powerful combinations to be achieved. Generally, the objects defined by their UUIDs in the exceptions field will be allowed to perform an action if the allowed flag is false, and prevented from performing that action if the allowed flag is true. That is, they will follow the opposite of the general policy for that definition. 28 28 40 +=== Special Values === 41 + 42 +There are a few special predefined values that are used by the permission system. They are: 43 + 44 +* All Users Group: The all users group is hard-coded into iSymphony to contain all users. You can use this to set global permissions on the clients. The UUID for the 'All Users' group is 21d97061-ff6a-11e1-a21f-0800200c9a66. 45 +* 'Owned' permission target: In many cases, an administrator may want to defined that users only have access to their "own" objects: their user, their extensions, their phone numbers, etc. In this case, setting the permission to 'Deny', with the special exception df41edec-2707-46eb-8b8f-146b01d9b29e will only give users access to their own objects. 46 + 29 29 = Root Resource Paths = 30 30 31 31 {{code}} 32 32 communication_manager/api/resource/core/{core_server_id}/permissions 33 -communication_manager/api/resource/core/getBySlug/{core_server_slug}/permissions 34 34 {{/code}} 35 35 36 36 = JSON Representation = 37 37 55 +{{code title="Core Server Permissions Enabled" language="js"}} 56 +{ 57 + "permissionsEnabled": false 58 +} 59 +{{/code}} 60 + 61 +Note: the above object is only used to enable or disable permissions. See the page on the core server configuration itself to query the status of the permissions. 62 + 38 38 {{code title="PermissionConfig" language="js"}} 39 39 { 40 40 "key": "cellPhoneOriginateTo", ... ... @@ -95,10 +95,31 @@ 95 95 96 96 |=(% colspan="2" %)(% colspan="2" %) 97 97 ((( 98 -{{{communication_manager/api/resource/core/{core_server_id}/permissions/userGroup/{user_group_id}}}} 123 +communication_manager/api/resource/core/{core_server_id}/permissions 124 +))) 125 +|=((( 126 +**Description** 127 +)))|((( 128 +Specifies whether permissions should be enabled or disabled for the entire core server. When disabled, no permission checks will be performed, so the rest of the settings specified in the permissions system will have no effect. Note that you must have a supported license installed to enable permissions. 99 99 100 -{{{communication_manager/api/resource/core/getBySlug/{core_server_slug}/permissions/userGroup/{user_group_id}}}} 130 +**Parameters**: 131 + 132 +* core_server_id: The UUID of the core server 133 + 134 +**Errors**: 135 + 136 +* 500 'Your license does not support permissions.': Returned if you do not have a license installed, or if your license does not support permissions. 101 101 ))) 138 +|=((( 139 +PUT 140 +)))|((( 141 +Sets whether permissions are enabled or disabled globally on the core server. 142 +))) 143 + 144 +|=(% colspan="2" %)(% colspan="2" %) 145 +((( 146 +{{{communication_manager/api/resource/core/{core_server_id}/permissions/userGroup/{user_group_id}}}} 147 +))) 102 102 |(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %) 103 103 ((( 104 104 **Description** ... ... @@ -125,8 +125,6 @@ 125 125 |=(% colspan="2" %)(% colspan="2" %) 126 126 ((( 127 127 {{{communication_manager/api/resource/core/{core_server_id}/permissions/userGroup/{user_group_id}/{key}}}} 128 - 129 -{{{communication_manager/api/resource/core/getBySlug/{core_server_slug}/permissions/userGroup/{user_group_id}/{key}}}} 130 130 ))) 131 131 |(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %) 132 132 ((( ... ... @@ -184,8 +184,6 @@ 184 184 |=(% colspan="2" %)(% colspan="2" %) 185 185 ((( 186 186 {{{communication_manager/api/resource/core/{core_server_id}/permissions/user/{user_id}}}} 187 - 188 -{{{communication_manager/api/resource/core/getBySlug/{core_server_slug}/permissions/user/{user_id}}}} 189 189 ))) 190 190 |(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %) 191 191 ((( ... ... @@ -213,8 +213,6 @@ 213 213 |=(% colspan="2" %)(% colspan="2" %) 214 214 ((( 215 215 {{{communication_manager/api/resource/core/{core_server_id}/permissions/user/{user_id}/{key}}}} 216 - 217 -{{{communication_manager/api/resource/core/getBySlug/{core_server_slug}/permissions/user/{user_id}/{key}}}} 218 218 ))) 219 219 |(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %) 220 220 ((( ... ... @@ -271,26 +271,35 @@ 271 271 272 272 = Curl Examples = 273 273 274 -=== Get === 314 +{{info}} 315 +The server ID in the below examples is 9280cd1c-4ad7-4ed9-ae8a-0648b0b45cf7. You will need to change this to the appropriate ID for your installation, as well as change other IDs. 316 +{{/info}} 275 275 318 +=== (% style="color: rgb(0,0,0);" %)Get all defined permissions for the 'All Users' group(%%) === 319 + 276 276 {{code language="bash"}} 277 - 321 +curl --user manager:manag3rpa55word -i -H "Content-Type: application/json" https://127.0.0.1:55050/communication_manager/api/resource/core/9280cd1c-4ad7-4ed9-ae8a-0648b0b45cf7/permissions/userGroup/21d97061-ff6a-11e1-a21f-0800200c9a66 278 278 {{/code}} 279 279 280 -=== (% style="color:rgb(0,0,0);"%)Update(%%)===324 +=== Get all defined permissions for a specific user === 281 281 282 -{{code language="bash"}}283 - 326 +{{code}} 327 +curl --user manager:manag3rpa55word -i -H "Content-Type: application/json" https://127.0.0.1:55050/communication_manager/api/resource/core/9280cd1c-4ad7-4ed9-ae8a-0648b0b45cf7/permissions/user/8a026a93-3201-4554-b993-32576a3b8ea5 284 284 {{/code}} 285 285 286 -=== Add===330 +=== (% style="color: rgb(0,0,0);" %)Deny the 'passwordChange' permission for the above user(%%) === 287 287 288 288 {{code language="bash"}} 289 - 333 +curl --user manager:manag3rpa55word -i -H "Content-Type: application/json" -X PUT -d '{"key":"passwordChange","allowed":"false"}' https://127.0.0.1:55050/communication_manager/api/resource/core/9280cd1c-4ad7-4ed9-ae8a-0648b0b45cf7/permissions/user/8a026a93-3201-4554-b993-32576a3b8ea5/passwordChange 290 290 {{/code}} 291 291 292 -=== Delete ===336 +=== Remove the 'passwordChange' permission for the above user === 293 293 338 +Note: this will not prevent the user from changing their password. It will cause the user to inherit the permission of any user groups they are a part of. 339 + 294 294 {{code language="bash"}} 295 - 341 +curl --user manager:manag3rpa55word -i -H "Content-Type: application/json" -X DELETE https://127.0.0.1:55050/communication_manager/api/resource/core/9280cd1c-4ad7-4ed9-ae8a-0648b0b45cf7/permissions/user/8a026a93-3201-4554-b993-32576a3b8ea5/passwordChange 296 296 {{/code}} 343 +{{/layout-cell}} 344 +{{/layout-section}} 345 +{{/layout}}