We have an application that uses section access to identify the user based on their NTNAME and reduce the data they can see based on their geographical permissions. This all works fine, locally, through access point, etc. as long as it hasn't been distributed via Publisher. The files that Publisher produces, once opened, identifies every user as a service account we have set up, instead of their windows login.
So prior to pubishing, if Joe Blow opens it, it recognizes him as DOMAIN\JOEBLOW, but after publishing, everyone is authenticated as DOMAIN\QVSERVICEACCOUNT.
This is the same whether going through access point or just going into the server and opening the QVW locally there.
Has anyone else run into a similar issue?
.png "Former Employee"){kind=icon}
