Re: MembershipProvider, ADAM and userProxy
- From: gely <gely@xxxxxxxxxx>
- Date: Fri, 15 Sep 2006 15:02:39 -0700
Ok: A bit more testing, and I find that, although I am calling my
assembly as the membership provider, I don't seem to be using it. Let
me explain:
If I rename or remove my assembly, or rename my custom membership class,
I receive an expected error from .NET.
If I change only the filter value, even to jibberish, .NET successfully
authenticates to ADAM.
This tells me that I am looking to my assembly for instantiation, but,
apparently, calling methods from elsewhere.
I created my custom provider by inheriting from the
ActiveDirectoryMembershipProvider and then overriding the FindUser
method. The rest of the code in my assembly is simply to support this
method. The new assembly lives in the bin directory of the .NET web
site.
Where'd I screw up? (Or is the better question "Where didn't I screw
up?"?)
- Thanks,
Geoff -
*** Sent via Developersdex http://www.developersdex.com ***
.
- References:
- Re: MembershipProvider, ADAM and userProxy
- From: gely
- Re: MembershipProvider, ADAM and userProxy
- Prev by Date: Re: MembershipProvider, ADAM and userProxy
- Next by Date: LDAP Auth Problem - COM interop
- Previous by thread: Re: MembershipProvider, ADAM and userProxy
- Next by thread: Re: LDAP Auth Problem - COM interop
- Index(es):
Relevant Pages
|