On Tue, 15 Feb 2005 03:36:08 -0800, "Lachlan James" <> wrote:
¤ Hi Paul,
¤
¤ Thanks for your reply. Unfortunately we are using a custom
¤ authentication system for this particular application
¤ because the built in ones don't fulfil our needs. This
¤ means using windows authentication & impersonation is not
¤ possible. Besides that, it is not recommended to do it
¤ that way for security reasons.
¤
¤ However towards the end of the article you posted it
¤ mentioned using COM+ serviced components to achieve this,
¤ so that's what I have done. I have a serviced component
¤ which I call from my asp.net app. The serviced component
¤ runs under a custom account which has access to the
¤ network share. This is the easiest & most secure way to do
¤ this I think.
¤
¤ For anyone else that is interested in doing this, below is
¤ a great article which explains how to do it and why it is
¤ the only viable option.
¤
¤
http://www.15seconds.com/issue/030926.htm
¤
¤ Lachlan
Yes I still use this type of mechanism for ASP and Visual Basic 6.0 components, although I kind of
moved away from COM+ since I moved to .NET.
Paul ~~~
Microsoft MVP (Visual Basic)