Nifty.  I'll have to check this out.  One of the things I had been looking
to do was set up one of our internal T5 webapps to auth against our Active
Directory instance.  I was going to look into using Atlassian Crowd for it,
but if your code makes it simple enough, that would be awesome.

-- 
Kevin


On 2/7/08 6:01 AM, in article [EMAIL PROTECTED], "Francois
Armand" <[EMAIL PROTECTED]> wrote:

> Hello,
> 
> I'm very happy (and glad) to announce a first working version of our
> InterLDAP project.
> 
> =========== Project info ============
> The mail is growing long, so there are the URL, description follows :
> 
> Main site : http://interldap.org
> 
> Demo site : http://wui.demo.interldap.org/wui-interldapDemo/login with
> for example [EMAIL PROTECTED] / efranck
> and demo howto : 
> http://federid.objectweb.org/xwiki/bin/view/Main/Demonstration (part of
> FederID, identity federation project that implements Liberty Alliance
> protocol)
> 
> The project is OpenSource (AGPLv3, don't troll on that, its our company
> policy)
> The svn of the project :
> http://forge.objectweb.org/plugins/scmsvn/index.php?group_id=162
> 
> You should be able, if the Saturn - Pluto -  Aldebaran  alignment  is
> good, to checkout the project  and give it a try with mvn jetty:run.
> Just try :
> # svn co 
> svn://svn.forge.objectweb.org/svnroot/interldap/interldap-wui-webapp/trunk/
> interldap-wui-webapp
> # cd interldap-wui-webapp; mvn jetty:run.
> It should build the project, get the dependencies, launch and embedded
> OpenDS as LDAP directory. After what, you only have to go to
> localhost:8080 and log with [EMAIL PROTECTED] / secret. If OW2 and
> Maven are in good mood.
> ================================
> 
> =========== Presentation ============
> 
> InterLDAP if a set of tools whose goals are to manage electronic
> identities thanks to LDAP directories.
> 
> One of the big tools of the set is a web interface to manage identities
> in an LDAP directory, kind of what Calendra does.
> Actually, the web interface have to deal with 4 kinds of topic :
> - make basic CRUD (Create, Retrieve, Update, Delete) operations on LDAP
> with an understandable interface for non-tech users, what suppose to :
>   * be able to generate really adaptable forms, because LDAP entries
> have no predefine structure like what you have in a DB ;
>   * be able to add a lot of meta information around LDAP schema to show
> understandable information ;
> - give to non LDAP-admin the possibility to manage the CRUD presentation
> (manage behavior of forms and metadatas), for example :
>   * show / disable fields ;
>   * make field multivaluated ;
>   * make fields mandatory ;
>   * edit meta information (fields names, info text, order, etc)
>   * etc
> - have the ability to define "business" rules link to these operation
> (entries post processing, etc)
> - define a powerful authorization system to enable rigths delegation,
> complex hierarchy management, etc. so that CRUD operations are *really*
> fine grained (down to the field level of entries, and may be different
> for each user).
> 
> So, why did I send a mail to the Tapestry list (as you can see, I'm very
> good to set up an unsustainable suspense...)
> We use T5 to build this web user interface (tada ! What a surprise !),
> and all the project is open source, so I think it's a rather
> non-standard and non trivial software implementation using Tapestry 5.
> 
> More precisely, one of the big difficulties of this kind of tool is the
> genericity it has to reach in the business layer : each company has its
> own hierarchy, business organization, history and exceptional cases to
> this complex set of rules. To achieve it, the project is broken in
> several modules, the top leveled of them being a T5 components framework
> that enable to build specific identity management software, tailored for
> the client.  And there is a first working implementation for a client.
> 
> The project is a "version 0", it lacks *a lot* of things, and especially
> a lot English documentation (actually, almost everything is in French
> :/), polishing (component generalization, behavior homogenization, etc),
> and of course any help would be much appreciated.
> 
> 
> Ok, now that I talk about all the business buzzwords, what's the
> interesting stuff, from a T5 point of view ?
> 
> 1/ A generic component framework and a specialized instantiation for the
> demo app
> that may be intersting to see how T5 facilitate my life with it's IoC /
> configuration possibilities
> 
> 2/ Composed and adaptable forms
> I did a lot of work around complex, composed and adaptable form. The
> center point of the application is editing entries whose structure is
> not predefine, a kind of specialized beanEditForm for LdapEntries. It as
> the same kind of possibilities (dynamically build, adaptable editors,
> etc) and some other nice feature. For example, Ldap entries may be
> multivaluated, so one the component is a "listeditor" that can edit List
> of object (edit each object, add new objects, remove object of the
> list). This component is also used to build composed search criterium
> (on the model of the search in thunderbird, for example).
>  
> 3/ A cool use of Tapestry implementation of strategy and pipeline
> pattern to decide what kind of post-processing an entry is subject to,
> and then process the pipeline of actions. The system is on the
> framework, specific configurations are contributed by implementation
> thanks to T5-ioc ;
> 
> 4/ A... certainly a score of other things.
> 
>   as I said, the project is open source, and we will be really glad to
> welcome new users or contributors.
> Any comments or question will be welcome !
> You may contact me on the Tapestry chan #tapestry on freenode (I'm
> fanf), or by mail.
> 
> Have a nice day, and a great Thanks to Tapestry 5 developers for this
> great framework.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to