Re: Serviced Component runs under ASPNET, not specified account

From: Gianluca Torta (GianlucaTorta_at_discussions.microsoft.com)
Date: 01/25/05

  • Next message: Shaker: "Access Authentication" 
    Date: Tue, 25 Jan 2005 01:17:05 -0800

    Dear Svein, thank you for your reply.

    Unfortunately the requirements I have make the Serviced Component the best
    way to obtain my goals (see thread "accessing remote resources from ASP.NET
    app").

    So my problem is now how to make my Serviced Component to run with identity
    "MYDOMAIN\MYUSER"

    -Gianluca

    "Svein Terje Gaup" wrote:

    > If you are using Windows Server 2003, you can configure an application pool
    > to be run as a user account of your choice. You can then assign your web
    > application to the application pool. Then check to see what account is being
    > used on your database.
    >
    > In ASP.NET you might also try to configure impersonation in web.config:
    > <identity impersonate="true" userName="DOMAIN\databaseuser"
    > password="123456" />
    >
    > This article describes a method for accessing resources on a server using a
    > copied ASPNET account:
    > http://weblogs.asp.net/mschwarz/archive/2003/03/31/4515.aspx
    > Perhaps you can use it for accessing your database?
    >
    > HTH,
    > Svein Terje Gaup
    >
    > "Gianluca Torta" <giatorta@gmail.com> wrote in message
    > news:21efe956.0501241104.21a525c6@posting.google.com...
    > > Cross posting since I had no reply yet from
    > > microsoft.public.dotnet.framework.component_services
    > >
    > > Hi all,
    > >
    > > I have an ASP.NET app and a Serviced Component that runs within a COM+
    > > app
    > >
    > > the Serviced Component is intended to access a remote database with an
    > > identity that is NOT <MACHINE>\ASPNET but an account MYDOMAIN\MYUSER
    > > that actually can access the remote database
    > >
    > > the COM+ app has been configured to RUN AS SERVER and I have specified
    > > in the identity tab that the app should run as MYDOMAIN\MYUSER
    > >
    > > however, when I open my ASP.NET app and click on the button which
    > > makes the call to the Serviced Component, I can see from SQL Server
    > > Profiler that the user which tried to access the remote DB is
    > > <MACHINE>\ASPNET
    > >
    > > for some reason, the COM+ app is not running as the account that I
    > > specify in the Identity tab but as the caller (which in this case is
    > > <MACHINE>\ASPNET)
    > >
    > > I guess I have some configuration problem, but I really couldn't
    > > figure out what it is:
    > > - I correctly wrote my Serviced Component
    > > - I strongly named the assembly .DLL produced by compiling the
    > > component
    > > - I registered the component with regsvcs.exe
    > > - my ASP.NET application references the DLL that has been strongly
    > > named
    > >
    > > Any suggestions would be welcome!
    > >
    > > Thanks in advance,
    > > -Gianluca Torta
    >
    >
    >

  • Next message: Shaker: "Access Authentication"
    • Quantcast