M
Marvin
We have an ASP.Net application that is being stored on a file share seperate from the IIS server machine. The application has been designed to use NT authentication (via User.Identity.Name) to control user access and security
We have IIS configured to list the site as a virtual directory under the website and a special "Connect As" user account and password was entered
The Problem: On development (with no file share), User.Identity.Name works as expected and returns the name of the browsing user. On test/deployment however, User.Identity.Name returns the name of the "Connect As" user that was used to establish the share between server and file system
We've tried to set up Active Directory delegation (machine level only) between the two servers but are still seeing the same results. Both servers are Win 2k servers on the same AD forest
My Questions going forward
1) Is it possible to have User.Identity.Name work across an network share like we are attempting?
If yes, the
2) Is delegation the answer to our problems and if so, what steps might we be missing
ie/ Do we need to set up any user level authentication? further configuration of IIS? special changes to web.config
Any other suggestions
We have IIS configured to list the site as a virtual directory under the website and a special "Connect As" user account and password was entered
The Problem: On development (with no file share), User.Identity.Name works as expected and returns the name of the browsing user. On test/deployment however, User.Identity.Name returns the name of the "Connect As" user that was used to establish the share between server and file system
We've tried to set up Active Directory delegation (machine level only) between the two servers but are still seeing the same results. Both servers are Win 2k servers on the same AD forest
My Questions going forward
1) Is it possible to have User.Identity.Name work across an network share like we are attempting?
If yes, the
2) Is delegation the answer to our problems and if so, what steps might we be missing
ie/ Do we need to set up any user level authentication? further configuration of IIS? special changes to web.config
Any other suggestions