We are having an issue with an ASP application using integrated authentication. The COM object and application are running under the domain however the authenticated user is being used on the share. See bullet on ASP vs ASP.NET on the KB article http://support.softartisans.com/kbview.aspx?ID=984 . (In ASP: If your application is set in IIS to use Basic, Digest or Integrated Windows authentication, FileUp will run as the authenticated user.) Is there a fix for this besides rewriting the app to use web.config etc? Even with setting up the COM object to run under a domain account that has full control to the share we are writing to it still tries to write to the share with the authenticated user and throws the error mentioned in the KB artcle above. Please Help!
firstname.lastname@example.orgI posted this exact text about a month ago and cannot find it on your forums site. Please advise.
First let me apologize that your post disappeared. I haven't heard an prior complaints of this, so we'll keep an ear out in case there is a problem with the forums.
Second, I'm a little confused by your post. It sounds like what you are saying is that you are trying to save the file to a network share, but you are encountering permissions problems. The KB article you referenced does refer to the permissions error you are getting, but there is a better article to read regarding saving to a network share.
Please read through this article and tell me if I've understood the problem correctly. If not, please tell me how your setup differs from the article so I can start thinking about this correctly.
How disappointing that you feel that I didn't take the time to read your post. I'm afraid I wasn't explicit enough with you on the purpose of the KB article. I meant to imply that you must use one of the methods listed in the article. This is a very frequently requested article, so admittedly, I did not completely read the KB article through, and I was under the impression that it explained that the REASON you need to use one of the methods described was because you cannot pass your NT credentials (from integrated authentication) 2 hops, meaing client to web server, webserver to fileserver/network share. I will make a note that this article needs both the version numbers addressed and a very clear statement explaining why integrated authentication is not listed as an option.
If any of these authentication scenarios do not work for you, then I would carefully look at the FileUpEE documentation. FileUpEE provides a secure means of performing 3 tier uploads, by making a separate SOAP-base request from the webserver.