In this article
Add a New Permission to an Already Existing Access Control List
URL
https://api.digitalvault.cloud/subscriptionconnection/{{connection_id}}/permissions/{{principal}}::{{permission}}/
Method
POST
URL Path Parameters
| Property | Description |
|---|---|
| connection_id | Id of the connection to modify permission for |
| principal | The principal to grant permissions to |
| permission | The permission level to grant |
Request Header Parameters
| Property | Description | |
|---|---|---|
| Authentication | Bearer {access_token} required |
Retrieve access token |
Response Body Parameters
| Name | Description |
|---|---|
| id | Id of the connection object |
| accesscontrolitems | Current list of access permissions for connection |
Errors
| Error | Description |
|---|---|
| 401 | Unauthorized |
| 400 | Update will leave ACL in invalid state |
| 403 | Forbiden. Possible causes: You do not have access to this endpoint (scope) You do not have access to this connection) |
| 504 | Timeout while attempting to write connection to storage repository |
Example
Request
POST https://api.digitalvault/subscriptionconnection/fakeconnectionid/permissions/fakeprincipal::desiredpermission
Response
{
"objectId": "TestConnId",
"accesscontrolitems": {
"sub:user:bob": "owner",
"org:jci.com": "readwrite",
"principal": "permission"
}
}
Notes
Where principal is one of sub:user:USERID, sub:dev:DEVICEID, sub:app:APPID, org:ORGID, group:ORGID:GROUPID and permission is one of owner, admin, readwrite, readonly.