Hi Vincent,
I guess some decisions that I would be interested in would be:
* Do you consider ESOE to be 'the' solution for XWiki authentication or
would you like to offer a mixed mode with say straight LDAP/database as
well.
* When is V2 starting development or due to be shipped? It might be
worthwhile simply targeting that version.
* Are you guys currently using Acegi or are you likely to use that or
something similar for v2?
Please excuse my ignorance but where might I find the v2 documentation.
regards,
Bradley
Vincent Massol wrote:
Hi Bradley,
I'm definitely +1 for all this below.
Let me know how you want to get started.
Maybe you could review the existing XWiki authentication/
authorization APIs and see if they are "powerful" enough so that an
ESOE bridge can be developed using them? I'm pretty sure we'll find
things missing but then we could make a stronger API. Actually since
we're talking about XWiki Architecture V2, it might be a good time to
review these APIs and propose some better ones, using ESOE as a use
case.
WDYT?
Thanks
-Vincent
On Sep 16, 2007, at 2:10 AM, Bradley Beddoes wrote:
Hi All,
We have a project called the Enterprise Sign On Engine (
http://esoeproject.org ) which is an Apache 2.0 licensed platform for
authentication, authorization and accountability for both internal
enterprise users and federated contexts. About 4 months ago I
talked to
some of you on this list and there was some interest in
integration, we
are now in a position to really try and bring this forward.
With ESOE integrated into Xwiki you would automatically get the
benefits
of using openID and Shibboleth. Xwiki would also get our ability to do
true single sign on from Active Directory enabled enterprise
clients. We
also have a very powerful XACML based authorization engine which
allows
some really unique flexibility in providing access control to content.
All said and done we are trying to provide a clean general purpose
solution to identity and federation that can be used across many
products without needing to continually reimplement this kind of
thing.
You don't have to write your own database for every application you
create we believe it should and can be the same way with identity.
We intend to support further technologies in the future such as
Yahoo's
BBAuth and Microsofts Identity Card. The really neat thing is that the
application side doesn't need to be changed at all when these new
options come on board for end users.
Please take a look around the website and I would really like to talk
further with you guys if there is an interest in doing some work
together.
regards,
Bradley
--
Bradley Beddoes
Lead Software Architect
Intient
http://intient.com - "Building intelligent open source solutions for
your enterprise"
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs