Re: MembershipProvider, ADAM and userProxy

Joe et all,

As suggested, I used reflector to create a custom membership provider -
with no changes to the original logic. It took more than a little
effort (seems like I had to disassemble and include almost half of the
original classes), but I finally got it to build and handle calls.

Using it in place of the ActiveDirectoryMembershipProvider in the
web.config file allowed for the authentication of ADAM users.

I then modified the filter for the DirectorySearcher to be:

searcher1.Filter =
"(&(objectCategory=person)(|(objectClass=user)(objectClass=userProxy))"
+ filter + ")";

I can still authenticate ADAM users, but the result for the AD users is
the same (unsuccessful login attempt) - and there is no trace of an
attempted authentication in the domain logs.

Do you think this could be a result of a needed property that the user
class has that the userproxy class does not?

Not sure how to proceed. Any suggestions would be helpful.

- Thanks -

*** Sent via Developersdex http://www.developersdex.com ***
.

Relevant Pages

  • Re: Complicated Fallback ASP.NET Security
    ... I think the main problem is that you really can't do Windows authentication ... Thus ADAM users can't have a WindowsPrincipal object. ... From there you could build out an IPrincipal object. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: ADAM
    ... Options for authentication are limited by the fact that native ADAM users ... passing those into the LDAP authentication call. ... For better advice on ASP ...
    (microsoft.public.windows.server.active_directory)
  • Re: Complicated Fallback ASP.NET Security
    ... Windows users against ADAM using its proxy authentication stuff, ... but there isn't any way to get a token for the ADAM users, ... users on our local intranet would be ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Complicated Fallback ASP.NET Security
    ... I'm trying to follow the example in 5A of that posting. ... managed authentication, and all but this one NTLM authenticated page ... >> some kind of Forms authentication as they aren't Windows users and can't be ... >> but there isn't any way to get a token for the ADAM users, ...
    (microsoft.public.dotnet.framework.aspnet.security)