To control whether the new ACE can be inherited by child objects, use the AddAccessAllowedAceEx function.
BOOL AddAccessAllowedAce( PACL pAcl, DWORD dwAceRevision, DWORD AccessMask, PSID pSid );
A pointer to an ACL. This function adds an access-allowed ACE to the end of this ACL. The ACE is in the form of an ACCESS_ALLOWED_ACE structure.
Specifies the revision level of the ACL being modified.
This value can be ACL_REVISION or ACL_REVISION_DS. Use ACL_REVISION_DS if the ACL contains object-specific ACEs.
Specifies the mask of access rights to be granted to the specified SID.
A pointer to the SID representing a user, group, or logon account being granted access.
If the function succeeds, the return value is nonzero.
If the function fails, the return value is zero. To get extended error information, call GetLastError. The following are possible error values.
||The new ACE does not fit into the ACL. A larger ACL buffer is required.|
||The specified ACL is not properly formed.|
||The specified SID is not structurally valid.|
||The specified revision is not known or is incompatible with that of the ACL.|
||The ACE was successfully added.|
The addition of an access-allowed ACE to an ACL is the most common form of ACL modification.
The AddAccessAllowedAce and AddAccessDeniedAce functions add a new ACE to the end of the list of ACEs for the ACL. These functions do not automatically place the new ACE in the proper canonical order. It is the caller's responsibility to ensure that the ACL is in canonical order by adding ACEs in the proper sequence.
The ACE_HEADER structure placed in the ACE by the AddAccessAllowedAce function specifies a type and size, but provides no inheritance and no ACE flags.
For an example that uses this function, see Starting an Interactive Client Process.
|Minimum supported client||Windows XP [desktop apps | UWP apps]|
|Minimum supported server||Windows Server 2003 [desktop apps | UWP apps]|
|Header||securitybaseapi.h (include Windows.h)|