I use a low level SSL tool to check to see whether SSL itself can be
negotiated for this type of thing. Sometimes there is something wrong on
the server with the private key on the cert and the server can't start the
handshake.
I don't know anything about eDirectory or I'd give you other pointers. :)
Best luck getting it figured out.
Joe K.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services
Programming"
http://www.directoryprogramming.net
--
"nelsonad" <nelsonad@[EMAIL PROTECTED]
> wrote in message
news:F2A7DED3-3937-42DB-8002-F4F724B64D4E@[EMAIL PROTECTED]
> Thanks for the reply Joe,
>
> I'm still not succeeding but I think I have environmental issues to
figure
> out, but you gave me some input to keep in mind for later.
>
> I tried downloading a trial of /n software IP*Works SSL V8 and pointing
> the
> sample site at my edirectory server, but it cant seem to talk to it
> either, I
> dont think this is the time or place to go over server configuration but
> I'm
> starting to think I screwed something up along those lines.
>
> Thanks again.
>
> "Joe Kaplan" wrote:
>
>> Do you need to use a different ****t when connecting to this server via
>> SSL?
>> Perhaps you need to specify "10.16.173:636" in your identifier?
>>
>> Normally, you should be accessing the server by hostname and should not
>> have
>> to override SSL verification as the server's certificate should be fine
>> and
>> should chain normally, but sometimes it is helpful to override the
>> verification.
>>
>> Note also that if you need to get this authentication approach to scale
>> effectively, you will need to reuse your existing LdapConnection across
>> multiple requests as you will run out of TCP wildcard ****ts if you open
>> and
>> close the connection over and over in rapid succession.
>>
>> Joe K.
>>
>> --
>> Joe Kaplan-MS MVP Directory Services Programming
>> Co-author of "The .NET Developer's Guide to Directory Services
>> Programming"
>> http://www.directoryprogramming.net
>> --
>> "nelsonad" <nelsonad@[EMAIL PROTECTED]
> wrote in message
>> news:8CCF5226-69B9-4709-9635-EB94B8F7188C@[EMAIL PROTECTED]
>> > Hi, I'm having some issues using S.DS.P LdapConnection to try and
>> > authenticate a login/password with a server hosting eDirectory.
>> >
>> > I've tried this LdapConnection con = new LdapConnection(new
>> > LdapDirectoryIdentifier(this.SearchRoot), new
>> > System.Net.NetworkCredential(this.tbUserName.Text,
>> > this.tbPassword.Text),
>> > AuthType.Basic);
>> > where
>> > SearchRoot = "10.16.173"
>> > username="customer"
>> > password="password"
>> > I can successfully log into iManager on the server hosting
eDirectory,
>> > but
>> > trying in the windows app i get an exception of:
>> > DirectoryOperationException - Confidentiality is required for this
>> > operation
>> >
>> > So i tried setting:
>> > con.SessionOptions.SecureSocketLayer = true;
>> > con.SessionOptions.VerifyServerCertificate = new
>> > VerifyServerCertificateCallback(ServerCallback);
>> >
>> > Where ServerCallback just returns true, and now i get an
LdapException
>> > errorcode 81 The LDAP server is unavailable.
>> >
>> > Thanks in advance for any advice you can offer, I've been searching
for
>> > quite a while now and keep coming up short.
>> >
>> > Adam
>>
>>
>>
|
