FRAMES | NO FRAMES | Description | Parameters | Response | Example |
URL: | http://server:port/arcgis/admin/services/[<folder>]/[<serviceName.serviceType>]/permissions/hasChildPermissionsConflict |
---|---|
HTTP Method: | POST |
Parent Resource: | Permissions |
Required Privileges: | Publisher or Administrator |
You can invoke this operation on the resource (folder or service) to determine if this resource
has a child resource with opposing permissions. This operation is typically invoked before adding
a new permission to determine if the new addition will overwrite existing permissions on the child
resources.
For more information, see the section on the
Continuous Inheritance Model.
Since this operation basically checks if the permission to be added will cause a conflict with permissions
on a child resource, this operation takes the same parameters as the
Add Permission operation.
Note:
Permission JSON Format | Description |
---|---|
principal | The name of the role for whom the permission is being assigned. |
permission | The permission JSON object. The format is described below. Format: { "isAllowed": <true|false>, "constraint": "" } |
General Paramters | Description |
f | The response format. The default response format is html. Values: html | json |
{ "hasChildPermissionsConflict":<true|false> }
http://server:port/arcgis/admin/services/Maps/permissions/hasChildPermissionsConflict permission={ "principal": "Analysts", "permission": { "isAllowed": true; "constraint": "" }, "childURL": "", "operation": "" }