Desired acl is split in to two if all apply_to keys are set to True for SLAG acls.

[MOHANRAJB]

API -/protocols/file-security/permissions/{svm.uuid}/{path}/acl

verb - POST

Trying to add an acl using the above API with body

{'access': 'access_allow',
'access_control': 'slag',
'apply_to': {'files': True, 'sub_folders': True, 'this_folder': True},
'propagation_mode': 'replace',
'user': 'SERVER12\\user1'}

but it configured as 2 acls, verified with API GET - /protocols/file-security/permissions/{svm.uuid}/{path}

{'access': 'access_allow',
           'access_control': 'slag',
           'advanced_rights': {... response skipped },
           'apply_to': {'sub_folders': True, 'this_folder': True},
           'user': 'SERVER12\\user1'},
{'access': 'access_allow',
           'access_control': 'slag',
           'advanced_rights': {... response skipped },
           'apply_to': {'files': True},
           'user': 'SERVER12\\user1'}

sometimes I find this behavior in file-directory acls too, is this expected one? REST API documentation does not have any info on this split behaviour.

Thanks,

Mohan

[RossC]

Hi @MOHANRAJB 

Looks like no one from the community has been able to answer your question so far. 

Just a suggestion, but we do have a fairly active #ontap-api channel in our NetApp Community Discord. Consider jumping onto that and asking your query there. 

You can access our NetApp Community Discord by heading to https://netappdiscord.com/ 

Hope this helps.