directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu" <>
Subject Re: [Triplesec] Thinking of a quick rewrite
Date Thu, 09 Aug 2007 23:50:21 GMT
Hi David,

On 8/9/07, David Jencks <> wrote:
> As far as I can tell from looking at svn basically nothing happened
> with this effort and from the original note now july is over so Alex
> doesn't have time to work on it any more?

No I intend to work on it but I realized that other things also need to be
to make this rewrite successful so I began working on those matters.  Now
I am a bit off line but will get back into the groove shortly.

I'm going to resume working on my sandbox triplesec-jacc.  I'm going
> to start by:

Well we discussed several issues with the schema and the way we use
groups.  There is more discussion required on this topic but feel free to
keep working on it since I have gained some insite on several things by
looking into this branch.  However also note that we have done some
pkg refactoring in the triplesec trunk already which also is not part of
any rewrite.

- change package to o.a.d.triplesec
> - change the OIDs to ones appropriate for apache.

Yeah I think we did this or need to definately.

- use maven-remote-resources-plugin for LICENSE/NOTICE files

Ohhhh more to learn from your branch :).

- remove admin ui with the intention of using ldap studio instead

Ahh yes we must do this eventually yes yes.

- use triggers instead of the interceptors (if I can figure out how
> and there is enough support for them in trunk)

Aye this will clean up much craptastic code.

- figure out how to use xbean-spring to configure the server

Ooohh this is where we differe I will start removign Spring and
start pushing the configuration into the DIT.  THis will reduce
more code in Tsec.

- model more of the NIST RBAC model (see
> rbacSTD-ACM.pdf)

Yes this is where I need to do some research as well.  But I have some
nice ideas here with how to deal with permission extension without
specificity for a specific language or platform.

My copy was running against apacheds 1.5 back in january but it
> doesn't compile any more due to big changes in interceptor
> interfaces.  I think that using triggers should make it less
> sensitive to such interface changes.

Aye agreed.

I'd be happy to move this either to the rewrite branch or to geronimo
> depending on whether the community thinks this direction is worth
> exploring or is definitely of interest only for geronimo.

I definitely think we can merge our efforts but we need better
collaboration.  I
blame myself for slipping here so please forgive me on this.  Also the
has been somewhat poor.  I think we can balance the jacc vision without
generalized usage.

One question I have is how to assign appropriate oids to the schema
> elements.  Previously I was just incrementing existing numbers but
> this is obviously not quite correct to get the OIDs to be correct for
> apache.  I'd definitely appreciate some advice on this point.

Take a look here:


I'd like to talk to you more about this and see if we can align better but I
blame you for forging ahead due to my lack of participation.  Let's just
working forward as you are stating and try to keep collaborating and
from one another.  I'm sure we can find some things of value during this
even if we cannot merge the code bases.  I think it would be premature to
our effort and short the potential to align at some point.


View raw message