netapp.ontap.na_ontap_file_security_permissions module – NetApp ONTAP NTFS file security permissions
Note
This module is part of the netapp.ontap collection (version 22.8.3).
You might already have this collection installed if you are using the ansible
package.
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install netapp.ontap
.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: netapp.ontap.na_ontap_file_security_permissions
.
New in netapp.ontap 22.0.0
Synopsis
Create, delete, or modify NTFS file security and audit policies of file or directory on NetApp ONTAP.
Note that ACLs are mached based on (‘user’, ‘access’, ‘access_control’, ‘apply_to’). In order to modify any of these 4 properties, the module deletes the ACL and creates a new one.
Requirements
The below requirements are needed on the host that executes this module.
Ansible 2.9 or later - 2.12 or later is recommended.
Python3 - 3.9 or later is recommended.
When using ZAPI, netapp-lib 2018.11.13 or later (install using ‘pip install netapp-lib’), netapp-lib 2020.3.12 is strongly recommended as it provides better error reporting for connection issues
a physical or virtual clustered Data ONTAP system, the modules support Data ONTAP 9.1 and onward, REST support requires ONTAP 9.6 or later
Parameters
Parameter |
Comments |
---|---|
An Access Control Level specifies the access control of the task to be applied. Valid values are “file-directory” or “Storage-Level Access Guard (SLAG)”. SLAG is used to apply the specified security descriptors with the task for the volume or qtree. Otherwise, the security descriptors are applied on files and directories at the specified path. The value slag is not supported on FlexGroups volumes. The default value is “file-directory”. This field requires ONTAP 9.10.1 or later. This defaults to “file_directory”. When state is present, all ACLs not listed in When state is absent, all ACLs are deleted when this option is absent. If this option is present, only ACLs matching its value are deleted. Choices:
|
|
A discretionary access security list (DACL) identifies the trustees that are allowed or denied access to a securable object. When a process tries to access a securable object, the system checks the access control entries (ACEs) in the object’s DACL to determine whether to grant access to it. |
|
Specifies whether the ACL is for DACL or SACL. Currently tested with access_allow, access_deny for DACL and audit_failure, audit_success for SACL. Choices:
|
|
An Access Control Level specifies the access control of the task to be applied. Valid values are “file-directory” or “Storage-Level Access Guard (SLAG)”. SLAG is used to apply the specified security descriptors with the task for the volume or qtree. Otherwise, the security descriptors are applied on files and directories at the specified path. The value slag is not supported on FlexGroups volumes. The default value is “file-directory”. This field requires ONTAP 9.10.1 or later. This defaults to “file_directory”. Choices:
|
|
Specifies the advanced access right controlled by the ACE for the account specified. |
|
Append Data. Choices:
|
|
Delete. Choices:
|
|
Delete Child. Choices:
|
|
Execute File. Choices:
|
|
Full Control. Choices:
|
|
Read Attributes. Choices:
|
|
Read Data. Choices:
|
|
Read Extended Attributes. Choices:
|
|
Read Permissions. Choices:
|
|
Write Attributes. Choices:
|
|
Write Data. Choices:
|
|
Write Extended Attributes. Choices:
|
|
Write Owner. Choices:
|
|
Write Permission. Choices:
|
|
Specifies where to apply the DACL or SACL entries. At least one suboption must be set to true. Suboptions that are not set are assumed to be false. With SLAGs, ONTAP accepts the three suboptions to be set to true, but creates 2 ACLs. This module requires the 2 ACLs to be present to preserve idempotency. See also |
|
Apply to Files. Choices:
|
|
Apply to all sub-folders. Choices:
|
|
Apply only to this folder Choices:
|
|
For each file or directory in the list, specifies that permissions on this file or directory cannot be replaced. |
|
Specifies how to propagate security settings to child subfolders and files. Defaults to propagate. This option valid only in create ACL. Choices:
|
|
Specifies the access right controlled by the ACE for the account specified. The “rights” parameter is mutually exclusive with the “advanced_rights” parameter. ONTAP translates rights into advanced_rights and this module is not idempotent when rights are used. Make sure to use Choices:
|
|
Specifies the account to which the ACE applies. Specify either name or SID. As of 21.24.0, the module is not idempotent when using a SID. To make it easier when also using |
|
path to SSL client cert file (.pem). not supported with python 2.6. |
|
Specifies the control flags in the SD. It is a Hexadecimal Value. |
|
Enable or disable a new feature. This can be used to enable an experimental feature or disable a new feature that breaks backward compatibility. Supported keys and values are subject to change without notice. Unknown keys are ignored. |
|
Override the cluster ONTAP version when using REST. The behavior is undefined if the version does not match the target cluster. This is provided as a work-around when the cluster version cannot be read because of permission issues. See https://github.com/ansible-collections/netapp.ontap/wiki/Known-issues. This should be in the form 9.10 or 9.10.1 with each element being an integer number. When Ignored with ZAPI. |
|
Specifies the owner’s primary group. Specify the owner group using either a group name or SID. |
|
The hostname or IP address of the ONTAP instance. |
|
Override the default port (80 or 443) with this port |
|
Enable and disable https. Ignored when using REST as only https is supported. Ignored when using SSL certificate authentication as it requires SSL. Choices:
|
|
For each file or directory in the list, specifies that permissions on this file or directory cannot be replaced. |
|
path to SSL client key file. |
|
The ontap api version to use |
|
Specifies the owner of the NTFS security descriptor (SD). You can specify the owner using either a user name or security identifier (SID). The owner of the SD can modify the permissions on the file (or folder) or files (or folders) to which the SD is applied and can give other users the right to take ownership of the object or objects to which the SD is applied. |
|
Password for the specified user. |
|
The path of the file or directory on which to apply security permissions. |
|
Specifies how to propagate security settings to child subfolders and files. Defaults to propagate. Choices:
|
|
Whether the specified file security permission should exist or not. When absent, all ACLs are deleted, irrespective of the contents of See Inherited ACLs are ignored, they can’t be deleted or modified. Choices:
|
|
Whether to use REST or ZAPI. always – will always use the REST API if the module supports REST. A warning is issued if the module does not support REST. An error is issued if a module option is not supported in REST. never – will always use ZAPI if the module supports ZAPI. An error may be issued if a REST option is not supported in ZAPI. auto – will try to use the REST API if the module supports REST and modules options are supported. Reverts to ZAPI otherwise. Default: |
|
This can be a Cluster-scoped or SVM-scoped account, depending on whether a Cluster-level or SVM-level API is required. For more information, please read the documentation https://mysupport.netapp.com/NOW/download/software/nmsdk/9.4/. Two authentication methods are supported
To use a certificate, the certificate must have been installed in the ONTAP cluster, and cert authentication must have been enabled. |
|
If set to This should only set to Choices:
|
|
ACLs may not be applied as expected. For instance, if Everyone is inherited will all permissions, additional users will be granted all permissions, regardless of the request. For this specific example, you can either delete the top level Everyone, or create a new ACL for Everyone at a lower level. When using Valid values are With SLAGS, ONTAP may split one ACL into two ACLs depending on the Choices:
|
|
Name of the vserver to use. |
Notes
Note
Supports check_mode.
Only supported with REST and requires ONTAP 9.9.1 or later..
SLAG requires ONTAP 9.10.1 or later.
When state is present, if an ACL is inherited, and a desired ACL matches, a new ACL is created as the inherited cannot be modified.
When state is absent, inherited ACLs are ignored.
The modules prefixed with na_ontap are built to support the ONTAP storage platform.
https is enabled by default and recommended. To enable http on the cluster you must run the following commands ‘set -privilege advanced;’ ‘system services web modify -http-enabled true;’
Examples
- name: Create file directory security permissions.
netapp.ontap.na_ontap_file_security_permissions:
state: present
vserver: svm1
access_control: file_directory
path: /vol200/newfile.txt
owner: "{{ user }}"
# Note, wihout quotes, use a single backslash in AD user names
# with quotes, it needs to be escaped as a double backslash
# user: "ANSIBLE_CIFS\user1"
# we can't show an example with a single backslash as this is a python file, but it works in YAML.
acls:
- access: access_deny
user: "{{ user }}"
apply_to:
files: true
hostname: "{{ hostname }}"
username: "{{ username }}"
password: "{{ password }}"
https: "{{ https }}"
validate_certs: "{{ validate_certs }}"
- name: Modify file directory security permissions.
netapp.ontap.na_ontap_file_security_permissions:
state: present
vserver: svm1
access_control: file_directory
path: /vol200/newfile.txt
acls:
- access: access_deny
user: "{{ user }}"
apply_to:
files: true
- access: access_allow
user: "{{ user }}"
apply_to:
files: true
hostname: "{{ hostname }}"
username: "{{ username }}"
password: "{{ password }}"
https: "{{ https }}"
validate_certs: "{{ validate_certs }}"
- name: Delete file directory security ACLs.
netapp.ontap.na_ontap_file_security_permissions:
state: absent
vserver: svm1
access_control: file_directory
path: /vol200/newfile.txt
acls:
- access: access_deny
user: "{{ user }}"
apply_to:
files: true
- access: access_allow
user: "{{ user }}"
apply_to:
files: true
hostname: "{{ hostname }}"
username: "{{ username }}"
password: "{{ password }}"
https: "{{ https }}"
validate_certs: "{{ validate_certs }}"