Re: Global.asax not allowing identity impersonation?
- From: "Doug" <spamworks@xxxxxxxxx>
- Date: 27 Jun 2006 13:03:06 -0700
bruce barker (sqlwork.com) wrote:
When you set Identity Impersonate=true, this means impersonate during the
request processing. Processing in global.asax is generally outside the
request processing. If you are on server 2003, you should use an application
pool, with identity with access to the serverserver. you could also specify
the account/password in the web.config (use the encrypted registry support).
-- bruce (sqlwork.com)
Not on Windows Server 2003 yet, so I guess I can't use an application
pool?
I tried, as Peter suggested, specifying the account/password in the
web.config... same error.
.
- References:
- Global.asax not allowing identity impersonation?
- From: Doug
- Re: Global.asax not allowing identity impersonation?
- From: bruce barker \(sqlwork.com\)
- Global.asax not allowing identity impersonation?
- Prev by Date: MasterPage really replaces frame?
- Next by Date: Re: MasterPage really replaces frame?
- Previous by thread: Re: Global.asax not allowing identity impersonation?
- Next by thread: Re: Global.asax not allowing identity impersonation?
- Index(es):
Relevant Pages
|