Re: [Bodington-developers] More LDAP Fun and Games

[Andrew B. <a.g...@le...>]

I used the Leeds AD without problem.

Let's see if it works outside the Leeds Brotherton Library.
You know who we are and you know where we live.

Let's put your code on one of our servers and test.

Aggie

-----Original Message-----
From: bod...@li...
[mailto:bod...@li...] On Behalf Of
Alistair Young
Sent: 29 July 2006 14:32
To: Bodington developers
Subject: Re: [Bodington-developers] More LDAP Fun and Games

> almost randomly the
> next() method called on the search results throws an exception
sometimes the assembled information on a subject is not absolutely ready
at the point of access. Are you specifically asking for certain
attributes?

> It looks like a fundamental problem handshaking within the
> LDAP protocol
how many source and destination machines have you tried it on? Have you
seen the AD logs? What version of AD is it?

> I think JNDI is far more likely to be well debugged against
> many different LDAP servers
no. In fact that's why I chose the openLDAP API as JNDI didn't work with
AD at the time. There was a published "bug" from Microsoft stating that
JNDI lookups would fail. As the openLDAP api worked, I used that =
instead.
I believe the bug is now fixed though when I last tried it, it JNDI =
still
didn't work.

> switch to JNDI and to the Sun LDAP provider is
> essential
> ...
> we can't be 100% certain that there isn't a problem at the Active
> Directory end of the LDAP
so what happens if you've still got the problem?, as you haven't
identiifed the problem. Before you go chucking stuff out let's make sure
it's not your AD that's at fault.

Can you try it from other machines?
Can you let us have the code and we can try it here against an AD?
What's your custom socket doing?

--=20
Alistair Young
Senior Software Engineer
UHI@Sabhal M=F2r Ostaig
Isle of Skye
Scotland

> Following on from previous posts....
>
> Michael and I have been having nasty problems with LDAP.  The
> authenticator discussed earlier on the list was deployed last Friday =
and
> the log is showing randomly occurring exceptions ever since. A
> connection, bind and search are carried out O.K. but almost randomly =
the
> next() method called on the search results throws an exception which
> indicates an internal error on the LDAP server but provides a message
> suggesting that a bind is required. Although nearly random there are
> some searches for particular users that always fail.
>
> I wrote a little application based on the authenticator which carries
> out the same operations in a loop.  Although unable to reproduce the
> same exception, other exceptions were thrown randomly. The nature of =
the
> exceptions strongly suggests programming errors in the Novell/OpenLDAP
> API (which perhaps only occur when connecting to Active Directory). I
> say this because the exceptions are not thrown in the main program
> thread but within LDAP API worker threads and refer to illegal access =
to
> semaphores. It looks like a fundamental problem handshaking within the
> LDAP protocol.
>
> Anyway, the point of all this explanation is that it leads me to the
> conclusion that a switch to JNDI and to the Sun LDAP provider is
> essential.  I think JNDI is far more likely to be well debugged =
against
> many different LDAP servers and more importantly if anyone has =
problems
> with the Sun provider in connection with their own little used LDAP
> server they may be able to plug in a specific provider for it.  Any
> thoughts on this?
>
> Jon
>
> P.S. we can't be 100% certain that there isn't a problem at the Active
> Directory end of the LDAP but another web service at Leeds, based on
> uPortal is successfully authenticating to it via JNDI.
>
>
> =
-------------------------------------------------------------------------=

> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to =
share
> your
> opinions on IT & business topics through brief surveys -- and earn =
cash
> =
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers
>


-------------------------------------------------------------------------=

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share =
your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
_______________________________________________
Bodington-developers mailing list
Bod...@li...
https://lists.sourceforge.net/lists/listinfo/bodington-developers