Customize UniInt Failover Sync File Permissions
Prior to UniInt v188.8.131.52, UFO sync files created during interface startup would inherit file permissions from their parent folder (assuming child inheritance had been enabled on the folder).
With UniInt v184.108.40.206, this behavior changed and now sync files created by the interface do not respect inheritance. Instead, they are created with a standard ACL containing only the local "Administrators" and "Users" security groups.
For users with complex file permission schemas, this change introduces additional, unnecessary configuration efforts that scale as interface numbers grow beyond the site-level.
would like to know the use case and design decision for this change. Why does the interface override a system setting for the folder? And why is this listed as an enhancement request if the "enhancement" is restoring previously defined behavior?
The behavior is now significantly different, it doesn't appear to follow standard conventions and there doesn't appear to be any documentation explaining the new behavior or reason(s) for the change.
It definitely is causing problems for our system and use cases because if the file is ever accidentally deleted or needs to be temporarily or permanently moved, manual intervention will now be needed to create the files, with the correct names, and with the correct (previously inherited) permissions. It no longer is automated and managed (as expected) by the interface. With more than a couple interfaces (we have over 50 easily), management of this is now a nightmare.