You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Alex Karasulu <ao...@bellsouth.net> on 2004/11/01 18:59:21 UTC
[Eve] Status
Hi all,
Good news! The Eve JNDI Provider is working pretty well and we're very
close to integrating all the peices. There are issues of course but its
very usable.
As you may know the Eve JNDI Provider is the Eve backend subsystem.
This JNDI Provider uses the LDAP namespace but it is not an LDAP
client. It translates JNDI calls to backing store operations on Eve
database partitions associated with naming contexts. These CRUD ops
work on entries stored within these partitions.
This provider is doing really well. There's however a long way to go
with verifying the correct operation of the complete set of JNDI
interfaces. We still need lots of test cases. Anyhow the JNDI provider
is at the heart of Eve. The front end networking code previously called
frontend is now the SEDA project which is a framework for any protocol
based on UDP and TCP. Trustin is groking the UDP part and fixing issues
with the TCP parts. Soon like within the next 48 hours or so we will be
adding code to JNDI provider to blow up SEDA with the LDAP hooks. These
hooks basically call the Eve JNDI provider to do their work.
Another really cool thing going on is on the Kerberos front. Enrique
has the Kerberos server working like a champion against the krb5kdc LDAP
schema using JNDI as the access API. We plan to create another subclass
of the default Eve InitialContextFactory implementation which also fires
up the Kerberos server that uses Eve as its JNDI LDAP backing store.
This 3 way integration is about to happen this week.
I'm very close to starting this but there are a few security issues I'm
trying to pound out with Eve right now. These matters deal with how Eve
treats Eve specific user accounts within the ou=system administrative
areas. There are some strict authorization rules that need to be put
into place there. Also I have one major JNDI bug to fix. This should
take me no longer than another day, maximum 2. Then it is all about
integrating these parts. This is all very exciting because we finally
get to see the fruits of our labor over the past year.
Alex
Re: [Eve] Status
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Tuesday 02 November 2004 16:26, Alex Karasulu wrote:
> Niclas Hedhman wrote:
> >Shouldn't Sun have some more or less official JNDI TCK for providers?
> Hey that would be a dream come true. I don't think anything like that
> exists but if you see one please let me know.
I guess you are right on the 'official side'... I 'm pulling some strings and
sees what floats up. :o)
Cheers
Niclas
--
+------//-------------------+
/ http://www.bali.ac /
/ http://niclas.hedhman.org /
+------//-------------------+
Re: [Eve] Status
Posted by Alex Karasulu <ao...@bellsouth.net>.
Niclas Hedhman wrote:
>On Tuesday 02 November 2004 01:59, Alex Karasulu wrote:
>
>
>
>>This provider is doing really well. There's however a long way to go
>>with verifying the correct operation of the complete set of JNDI
>>interfaces. We still need lots of test cases.
>>
>>
>
>Shouldn't Sun have some more or less official JNDI TCK for providers?
>
>
>
Hey that would be a dream come true. I don't think anything like that
exists but if you see one please let me know.
>Keep up the good work.
>Niclas
>
>
Thanks,
Alex
Re: [Eve] Status
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Tuesday 02 November 2004 01:59, Alex Karasulu wrote:
> This provider is doing really well. There's however a long way to go
> with verifying the correct operation of the complete set of JNDI
> interfaces. We still need lots of test cases.
Shouldn't Sun have some more or less official JNDI TCK for providers?
Keep up the good work.
Niclas
--
+------//-------------------+
/ http://www.bali.ac /
/ http://niclas.hedhman.org /
+------//-------------------+