From: "Francesco Chicchiriccò" <[email protected]>
On 23/07/2012 15:15, Jacques Le Roux wrote:
From: "Francesco Chicchiriccò" <[email protected]>
On 23/07/2012 12:43, Mark Struberg wrote:
Hi!
Don't think that ApachEE fits good for Etch. ApachEE is focusing
purely on our Java EE core technologies stack.
Same for Syncope, though it's much closer. Would be nice to explain
the overlaps/difference between Syncope and Shiro btw ;)
Uh, quite easy, indeed: Shiro is an Access Manager [1] while Syncope is
an Identity Manager [2]
Access Management is more about authentication, Single SignOn,
Federation, ...
Identity Management is more about user provisioning, password
management, ...
These two areas can be easily confused because in almost every
application domain they are tightly connected; think, for example, that
Syncope roadmap [3] contains an integration path with Shiro.
Maybe we could have a 2nd track which supplements the ApachEE core
track and showcases the different "Enterprise Integration"
scenarios.
This sounds reasonable to me and in the direction of the aborted
"Integration & Service APIs" track [4].
Regards.
Thanks for this answer,
Pretty useful, we (at least I) hope to use both of them in OFBiz...
one day...
BTW how Syncope relates to NIST http://csrc.nist.gov/groups/SNS/rbac/ ?
Hi Jacques,
thanks for your interest.
At the moment there is no direct relation with "external" Role Based
Access Control (RBAC), while Syncope is implementing such approach for
its own internal authentication and authorization model; anyway it is
something noticeable for the roadmap: why don't you start a thread on
[email protected]?
It's too early yet. We are just restructuring the core. And anyway I have not much availabilit to put in it at the moment. But I
keep the idea!
Jacques
Regards.
Maybe that would also fit to Camel and it's parts?
In general: we have quite a few projects which sound like the same
on the first glance, but are heavily different at the end:
Syncope/Shiro
Jackrabbit/Sling
Accumulo/Cassandra
...
Would be interesting to better explain the differences? Not sure if
this is an easy to cover conference topic though, but I got
lots of questions regarding the focus of a few projects.
[1] http://en.wikipedia.org/wiki/Web_access_management
[2] http://en.wikipedia.org/wiki/Identity_management
[3]
https://cwiki.apache.org/confluence/display/SYNCOPE/Roadmap#Roadmap-3.0.0%28Maggiore%29
[4]
http://mail-archives.apache.org/mod_mbox/www-apachecon-discuss/201206.mbox/%3C4FE2DB7A.20103%40apache.org%3E
----- Original Message -----
From: Mohammad Nour El-Din <[email protected]>
To: [email protected]
Cc:
Sent: Monday, July 23, 2012 11:28 AM
Subject: Re: Apachecon EU 2012 - Which Track for a middleware as
Apache Etch?
Hi Martin
On Mon, Jul 23, 2012 at 9:03 AM, Martin Veith
<[email protected]>wrote:
Hi all,
the Apache Etch (incubating) team would like to give a talk about
the
project at ApacheCon EU 2012. As we are currenlty preparing our
proposal we
are asking ourself which track fits the best.
Etch is a middleware framework to build and consum network
services. (for
more details: http://incubator.apache.org/etch)
In my opinion, a middleware is not a classical Web Infrastructure
or Cloud
topic. Maybe Apache Daily? What do you think?
What about http://www.apachecon.eu/tracks/#apache-ee
IMO this fits in the enterprise applications related category more
specifically integration and services oriented software development
--
Francesco Chicchiriccò
ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/
--
Francesco Chicchiriccò
ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member
http://people.apache.org/~ilgrosso/
