"ADSVALUE not implemented" error, LDAP, dotNet, and more!

I've read every single posting on ADSVALUE, and possibly every single
posting on LDAP and .NET/dotNet, but I am still having problems
debugging an LDAP authentication issue.

The setup: We are using a .Net application to authenticate, using SSL,
with an LDAP directory on port 636. In the .Net code, the
DirectorySearcher searches on a DirectoryEntry. It uses the FastBind
AuthenticationType.

Sometimes it works and sometimes it doesn't. In almost every scenario,
if the application has not been used for several hours and someone
attempts authentication, it fails with the "ADSVALUE type is not yet
implemented" error message. Interestingly, if we wait about 30 minutes
and do not attempt any more logins, the error goes away.

Could the errors be related to FastBind? Should it be using
AuthenticationTypes.SecureSocketLayer instead?

Finally, the Microsoft documentation mentions that for FastBind, "ADSI
does not attempt to query the Active Directory objectClass property and
thus only exposes the base interfaces supported by all ADSI objects
instead of the full object support". I am clueless as to what this
means - can someone translate this into clearer English? What does it
matter if the objectClass property is not initially queried? Since our
LDAP has custom attributes, could this behaviour of FastBind cause the
error we received?

.

Relevant Pages

  • Re: "ADSVALUE not implemented" error, LDAP, dotNet, and more!
    ... this stuff comes down to whether your LDAP directory is using ... attempts authentication, it fails with the "ADSVALUE type is not yet ... Could the errors be related to FastBind? ... matter if the objectClass property is not initially queried? ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Directory Services, LDAP or similar
    ... In other projects, we managed the user authentication by creating tables that define all users and its allowed capacities, then the application queryies that data to verify if a user has access to some feature or not. ... The above ID and password are sent to the service at login time. ... They are using Novell eDirectory at the enterprise level; yes it's LDAP. ... We already do that for three different DB servers; ...
    (borland.public.delphi.non-technical)
  • Re: noob on slapd with sasl errors
    ... If I may share advice based on my own trials & tribulations with LDAP ... people who need network authentication and the current state of ... context of network authentication, LDAP really is just a protocol used ... I have no idea how sasl works and why it is needed here, or even more, ...
    (Ubuntu)
  • Re: Directory Services, LDAP or similar
    ... we managed the user authentication by creating tables ... The above ID and password are sent to the service at login ... Novell eDirectory at the enterprise level; yes it's LDAP. ... servers; ...
    (borland.public.delphi.non-technical)
  • Re: Recommended strategy for providing access to web apps via Inte
    ... LDAP is an ugly solution on the public internet, ... These federated authentication protocols are designed to address these ... Co-author of "The .NET Developer's Guide to Directory Services Programming" ...
    (microsoft.public.windows.server.active_directory)