Note that there are some explanatory texts on larger screens.

plurals
  1. USAndrew
    primarykey
    data
    text
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COThanks for that, I also decided to re-engineer to use the System.DirectoryServices.Protocols assembly in the end. Granted it's a little procedural but having worked with Win32 LDAP libraries before it feels a lot closer to the metal. And I feel more confident that the code will be adaptable to future requirements than code using the ADSI-based System.DirectoryServices.
      singulars
    2. COHi. Thanks for the input, much appreciated. I'm also coming to the conclusion that the whole problem could be tackled much more reliably using the lower-level Protocols namespace. What I have noticed is that when the self-signed certificate is correctly added to the local machine certificate store I can set the VerifyServerCertificate callback to validate the cert with success, something like " delegate(LdapConnection connection, X509Certificate certificate) { return new X509Certificate2(certificate).Verify() }", but I still get no joy with DirectoryEntry.
      singulars
    3. COI have also noticed that I get the following in my system events during failed DirectoryEntry attempts : "The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is MYSERVER.MYDOMAIN.CO.UK. The SSL connection request has failed. The attached data contains the server certificate." I'm looking into that now, but I think the answer is still the Protocols namespace for maximum confidence and reduced environmental dependency.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload