Inherit new ACLs from destination root folder

[researchcomputing]

I'm using SuperFlexible to move data from an incoming directory (source) which has different ACLs than the destination directory. I'd like the data to inherit the ACLs from the root destination directory and not be copied with the ACLs from the source directory. I can't seem to find a way to do this with SuperFlexible. Does anyone know how to do this with SF?

Thanks

[superflexible]

Hello,

by default, the program does not copy any ACLs with the files, so they should automatically inherit the ACLs on the destination. Just makes sure you haven't chosen "Process Security And Shares" on the Special tab sheet.

[researchcomputing]

Hello,

That is not the behavior we are seeing. We have "Process Security And Shares" on the Special tab sheet unchecked. The destination directory is set to inherit permission but the all the data superflexible is copying/moving has the ACL's from the source directory. The check box the file(s) "Include inheritable permissions from this object's parent" is check. But none of the destination's ACLs are present.

Thanks,

[superflexible]

It works fine here. If "Process Security and Shares" is unchecked, then the program will behave as though the file was copied with Windows Explorer. So if you get it to work in Windows Explorer, it will work with the synchronizer too.

It may also make a difference if you choose "Windows API Copying Function" on the tab sheet Files->More.

[researchcomputing]

Hello,

We have enabled "Windows API Copying Function" and test again and ACLs on the files are still the same as the source directory. If we do a manual move in Windows Explorer we get the expected & desired behavior. Why isn't this working with the the synchronizer?

Thanks,

[superflexible]

I don't know. I haven't had any support requests of this type in the past 8 years. Maybe it depends on the user account that the service is running under.

[researchcomputing]

Hi, The account used to run the service and to do the manual window's explorer is the same. Having the ACLs inherent from the destination directory is a critical part of our work. What other troubleshooting steps can we try?

[superflexible]

One thing you could do is try if the older version 4.97 behaves any different.

I don't have any other ideas right now but if you remind me in May I may be able to implement something to verify the inheritance. Surprisingly, this has never been a problem though.

[researchcomputing]

We've tried this with several different versions, different systems & different users and every time the permissions were copied over from the source. If we do a manual windows copy or move we get the expected and desired behavior.

[superflexible]

FYI, we will do a remote desktop session with the customer to try to resolve this issue and report back here.