Set up IIS virtual directory to UNC
I need to setup a IIS virtual directory on an XP machine to access a UNC path on a Windows 2003 file server. I must use a domain account and all computers are in a trusted domain. How do I accomplish this goal? This is just for dev right now. If more information is required please let me know.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Basically a developer is working on an in-house content management system. Through .net the application will access a file share and publish staged files to the web server after they are approved. To me it seems this should be done through a virtual directory but this does not have to be the case.
Anyway, I found this article which is very similar to what the MS one explains with a little more detail and some pictures to help with the visuals. http://www.codeproject.com/KB/aspnet/UNC__Access_Network_file.aspx I cannot use local accounts and having a domain password in plain text in the .net for impersonation really bothers me.
I guess, what is the best way to achieve my goal? The virtual directory or another method? If it is the virtual directory how can I suggest the developer protect the user credentials from being plain text.
Anyway, I found this article which is very similar to what the MS one explains with a little more detail and some pictures to help with the visuals. http://www.codeproject.com/KB/aspnet/UNC__Access_Network_file.aspx I cannot use local accounts and having a domain password in plain text in the .net for impersonation really bothers me.
I guess, what is the best way to achieve my goal? The virtual directory or another method? If it is the virtual directory how can I suggest the developer protect the user credentials from being plain text.
Hi,
I think that what you are describing is probably something different than the usual purpose of mapping IIS virtual directories.
I suspect that you would probably want to use the application framework itself (rather than IIS) to access the remote unc location/s.
To secure clear text passwords, use SSL on the web site.
Cheers.
I think that what you are describing is probably something different than the usual purpose of mapping IIS virtual directories.
I suspect that you would probably want to use the application framework itself (rather than IIS) to access the remote unc location/s.
To secure clear text passwords, use SSL on the web site.
Cheers.
ASKER
We found a way around this...without the virtual directories. The primary problem was the developer computer and this could be setup as you described with a virtual directory and local accounts. But that is against our security policy. We resolved this through using a limited service account (domain user) and using .net impersonation and an encrypted .config user/password. It seems to be working ok thus far.
ASKER
Self-resolved but the proposed solution did help further research.
ASKER