Re: Membership functions connect to Sql Server as Process Identity, not user identity??
- From: Dominick Baier [DevelopMentor] <dbaier@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 16 Apr 2006 08:22:49 +0000 (UTC)
not sure whats your problem - it compiles fine here -
SR is internal - maybe change it to public / don't put it in App_Code
the impersonation code in question is (in SqlConnectionHolder.Open)
if (revertImpersonate) {
using (HostingEnvironment.Impersonate()) {
Connection.Open();
}
}
else {
Connection.Open();
}
just change it to
Connection.Open();
(not tested)
---------------------------------------
Dominick Baier - DevelopMentor
http://www.leastprivilege.com
Thanks again, I was wondering where the code was to change
impersonation. Now I have to figure out how to take the
SqlMembershipProvider, make my changes, and get it to compile
correctly. I tried to just copy all the source that microsoft provided
and put it in my app_code folder and change my settings in the
web.config file, but I got a compile error saying Microsoft.Samples.SR
is inaccesible due to its protection level. I don't know what this
means, so back to googling for answers.
.
- Follow-Ups:
- References:
- Prev by Date: Re: Membership functions connect to Sql Server as Process Identity, not user identity??
- Next by Date: Re: Membership functions connect to Sql Server as Process Identity, not user identity??
- Previous by thread: Re: Membership functions connect to Sql Server as Process Identity, not user identity??
- Next by thread: Re: Membership functions connect to Sql Server as Process Identity, not user identity??
- Index(es):
Relevant Pages
|
|
