J
JimN
I have an ASP.Net app for which I want to be able to log
events to the Windows 2000 server event log under a special
log name. I encountered the initial security exceptionwhen
I first tried this in code and then did some research on
the subject. I think I've found two seperate ways to
accomplish what I want to do:
1. Use "sandboxing" by writing a class library in a
strong-named assembly that I install in the GAC which I
then call into from my ASP.Net app.
2. Use wrapped Win32 API calls to perform impersonation,
which, I understand, requires that I grant "Act as Part of
Operating system" priviledge to the ASPNET user.
Which do the users of this group suggest I use for the best
security and portability to other, possibly new, Windows
servers?
events to the Windows 2000 server event log under a special
log name. I encountered the initial security exceptionwhen
I first tried this in code and then did some research on
the subject. I think I've found two seperate ways to
accomplish what I want to do:
1. Use "sandboxing" by writing a class library in a
strong-named assembly that I install in the GAC which I
then call into from my ASP.Net app.
2. Use wrapped Win32 API calls to perform impersonation,
which, I understand, requires that I grant "Act as Part of
Operating system" priviledge to the ASPNET user.
Which do the users of this group suggest I use for the best
security and portability to other, possibly new, Windows
servers?