Re: LDAP Authentication



Thanks Joe for your responses. Not exactly what I was hoping to hear, but did
shed some light on the problem at hand. Building my own directory sounds like
the best course of action. Hopefully that will be straightforward.

Regards,
--
Hutty


"Joe Kaplan" wrote:

The web server you are running this on shouldn't matter. What matters is
the backend LDAP store you are trying to use. In your case, the store is
not supported.

The membership provider framework is extensible, so you could write your own
LDAP auth membership provider that is coded to work with Sun One. You could
use S.DS.Protocols for this which is a lower level, less "MS-specific" LDAP
API.

You can use a tool like reflector to reverse engineer the existing provider
to see how it works.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
"Hutty" <Hutty@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A55F761D-15A9-4254-B698-282200C4206A@xxxxxxxxxxxxxxxx
Thanks for the reply Joe.

Actually, I am trying to connect using Visual Web Studio 2008. Do I need
to
ask for permission to connect using this provider?

If I can't connect using this method, what are my alternatives?

Thanks
--
Hutty


"Joe Kaplan" wrote:

I think it is exactly as it says. The provider is specifically designed
only for AD and ADAM. You mentioned you had Sun One.

Are you asking how it is that the provider can tell your directory is not
AD
or ADAM?

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services
Programming"
http://www.directoryprogramming.net
"Hutty" <Hutty@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:66A1AD76-FD58-4139-97C6-14BD9CD5425E@xxxxxxxxxxxxxxxx
Hi,

I am trying to authenticate user and password against Sun One LDAP. I
am
getting the following message when trying to connect:

This provider can target only Active Directory and ADAM directories

Any ideas why I am getting this messages?
Here's my connecting info:

<add name="ADConnectionString"
connectionString="LDAP://ldap-r.hutty.edu:123/ou=people,dc=hutty,dc=edu"/>

connectionStringName="ADConnectionString"
connectionUsername="cn=user1,ou=roles,dc=hutty,dc=edu
" connectionPassword="password"/>

Thanks


--
Hutty




.



Relevant Pages

  • Re: Using Active Directory for Centralized Authentication
    ... Thanks for the reply Joe. ... We may have several applications pointing to ... LDAP and it's unlikely we'll use ASP.net or IIS. ... Co-author of "The .NET Developer's Guide to Directory Services Programming" ...
    (microsoft.public.windows.server.active_directory)
  • Re: Secure External LDAP Query into Our Active Directory
    ... Thank you for your response Joe. ... authenticate to our domain via LDAP over SSL when they go to Blackboard's ... Co-author of "The .NET Developer's Guide to Directory Services Programming" ...
    (microsoft.public.windows.server.active_directory)
  • Re: LDAP Authentication
    ... What matters is the backend LDAP store you are trying to use. ... The membership provider framework is extensible, so you could write your own LDAP auth membership provider that is coded to work with Sun One. ... Co-author of "The .NET Developer's Guide to Directory Services Programming" ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: LDAP Authentication
    ... One of the things with the membership provider framework is that you don't actually have to implement every single interface member when building your provider. ... Most of the complexity stems from managing all that stuff and figuring out the LDAP details to make that work on your given directory platform. ... Co-author of "The .NET Developer's Guide to Directory Services Programming" ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Querying AD via LDAP w/ simple authentication - need domain name?
    ... postoffice-type address list running under 2003's LDAP? ... > that you can't use the DN with a secure bind. ... > Joe K. ... >> API will let you use all three for a simple bind... ...
    (microsoft.public.windows.server.active_directory)