Re: [Bodington-developers] LDAP Authentication - OpenLDAP versus JNDI

[Alistair Y. <ali...@sm...>]

> Alistair[weird] = Jon[Ingenious]
I can hear your trumpet from here Jon ;) I suspect any potential bugs  
are either due to only UHI using it so we don't know what other  
setups there are or the incredible ingenuity of the interface simply  
overwhelming a mere mortal such as myself ;)

> It has to be deployed on Saturday
my sympathies

> It
> initially has some hard wired extras
which eventually lead to new VLEs!

> whether the user is a student
> or staff
yes, that's a point - that will never be interoperable. That's what  
shibboleth is designed for. It makes it easier to map attributes such  
as this to groups etc.

> I think I found another way to make it work using a custom
> socket factory
genius, pure genious. I have visions of you being carried through the  
streets of Leeds in a sedan chair, lightly wafted by ostrich  
feathers, flinging scraps of scribbled arcana to the crowds. When's  
the film?

Seriously, if you've only got until Saturday why worry about sockets?  
The LDAP server should have a default idle timeout that would cover  
in the first instance.

Alistair


On 19 Jul 2006, at 14:01, Jon Maber wrote:

> Alistair Young wrote:
>>> If credentials are set then valid is set false ... set valid=true
>>> when the authentication failed
>>>
>> this kind of weirdness!
>>
> Alistair[weird] = Jon[Ingenious]   ;-)
>>
>>> eventually I'll generalise it and commit
>>> back to the release version
>>>
>> can you not generalise it from the start?
> Two reasons not to - 1) It has to be deployed on Saturday. 2) It
> initially has some hard wired extras, i.e. whether the user is a  
> student
> or staff is found by looking at the length of an attribute in the LDAP
> record and because I'm not 100% confident about the user names  
> currently
> in the Bodington database always corresponding to the user names in  
> the
> LDAP extra checks are made - payroll number and student number must
> match.  So, before it replaces the current authenticator it needs  
> these
> kinds of things separated out and I don't have time to do it now.
>
> Another problem - the nice constructor with the timeout option doesn't
> do what I thought it would!  The number is used to set the socket data
> reading timeout which is not the same as the socket connection  
> timeout.
> However, I think I found another way to make it work using a custom
> socket factory.
>
> Jon
>
>
> ---------------------------------------------------------------------- 
> ---
> 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=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers