Has Child Permissions Conflict

URL:
https://<root>/services/permissions/hasChildPermissionsConflict
Methods:
POST
Required Capability:
Access allowed with any authorized privilege
Version Introduced:
10.1

Description

The hasChildPermissionsConflict determines if this resource (folder or service) 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 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.

Request parameters

ParametersDescription

principal

The name of the role for whom the permission is being assigned.

Example
1
principal=Analysts

f

The response format. The default response format is html.

Value: html | json | pjson

Example usage

The following is a sample POST request for the hasChildPermissionsConflict operation:

1
2
3
4
5
6
POST /webadaptor/admin/services/Maps/permissions/hasChildPermissionsConflict HTTP/1.1
Host: machine.domain.com
Content-Type: application/x-www-form-urlencoded
Content-Length: []

principal=Analysts&isAllowed=on&constraint=&childURL=&operation=&f=pjson

JSON Response example

1
2
3
{
  "hasChildPermissionsConflict": false
}

Your browser is no longer supported. Please upgrade your browser for the best experience. See our browser deprecation post for more details.

You can no longer sign into this site. Go to your ArcGIS portal or the ArcGIS Location Platform dashboard to perform management tasks.

Your ArcGIS portal

Create, manage, and access API keys and OAuth 2.0 developer credentials, hosted layers, and data services.

Your ArcGIS Location Platform dashboard

Manage billing, monitor service usage, and access additional resources.

Learn more about these changes in the What's new in Esri Developers June 2024 blog post.

Close