What is the Impact of Distribution Task on Security
We are migrating from a standalone server to a separate Publisher /QVS Deployment. As part of this change we are introducing a Distribution Task as opposed to having The Source Document Refresh in situ (Same Source/Mounted Folder)
However, when introducing a Distribution Task it appears to impose some changes on the Security. Section Access on the document in question is designed to use OS_USER and when just a reload task is defined, Users can gain access to their document according to their Windows Login. However, when a distribution task is added to distribute to a QVS then the same users now get prompted for user credentials.
Is this expected behaviour and how can I keep the same functionality that existed prior to this change, namely Section Access Data Restriction based on OS_USER.