Mary, Joel, and interested parties,
Great! I've set up a conference call for 2PM EST next
Tuesday (December 6) (i.e. 11AM Pacific Time). Use
1-303-928-3232, ID 6053141# for the call.
Joel, It would be wonderful for you to
participate.
Mary, I have described ALF's interest in Higgins in my
email at the bottom of this thread. So I would like to suggest the
following agenda topics:
1. Describe ALF's near term and long term
requirements for security. (Brian and the ALF attendees)
a) Short
term: single sign-on (via users using tools and via web service
invocations from ALF Service Flows (BPEL orchestrations) involving a common
identity server
b) Mid term: authorization (i.e. who is allowed to invoke a Service
Flow)
2. Describe the state of Higgins (Mary and the
Higgins attendees)
a) What is
in the milestone you just released?
b) What is
the relationship between Higgins and other open source security
projects?
3. What is the
intersection between what Higgins is working on and what ALF is doing for
security
a) What is
the timeframe (i.e. do the roadmaps for ALF and Higgins coincide (or can we
align them?))
b) What
capabilities will Higgins provide (or adopt from other projects), such as an
identity server
c) Are
there other synergies (e.g., can Higgins leverage any of the security work
underway for ALF)
4. Identify Action items/next
steps
Regards,
Brian
Brian Carroll Serena
Fellow Serena (ofc) (503) 617-2436 (cell)
(503) 318-2017 bcarroll@xxxxxxxxxx
Brian,
Mary,
I was
about to ping Higgins myself wrt Compuware's project when I noticed this thread.
Would it be possible for me to participate in this call as well? I'm on EST as
well, so whatever time you all set up will work fine for
me.
Thanks,
Joel
Hawkins
Good to hear from
you. We have just provisioned our initial Higgins milestone
0.2 code on Eclipse, and were preparing to get
back to those projects that had expressed an interest in Higgins, so your
timing is perfect. The initiators of the Higgins project are on
the East Coast. The afternoon of Tuesday 6th could work on
this end. We also have a lot of flexibility on December 7, 8, and
9. Let me know if any of these days could work for
you.
We will take a look
at your latest ALF documents.
-----Original
Message----- From: Brian
Carroll [mailto:BCarroll@xxxxxxxxxx] Sent: Wednesday, November 30,
2005 12:56
PM To: mary@xxxxxxxxxxxxxxxxx;
higgins-dev@xxxxxxxxxxx Cc: Ali Kheirolomoom; Tim
Buss Subject: Eclipse
Higgins and Eclipse ALF projects
Hi Mary (and Higgins team
members),
I work on the Eclipse
Application Lifecycle Framework (ALF project). Mike Malinkovich had sent an
email introducing us. The ALF team has been making great progress
putting the foundation for development tools to interoperate in far richer
ways than previously possible. And now that we have the "basic
plumbing" working, we are turning our attention to the topic of single
sign-on among development tools that communicate via web
services.
I've spent some time reading the
material and wiki on Higgins, and my impression is that Higgins is concerned
with federated identity and rights for accessing identity information, and
that is certainly has some intersection with what ALF will need.
We have been looking at open source projects, such as JOSSO, Shibboleth (and
its component OpenSAML) among others, and would like to start a dialogue on
how ALF and Higgins can work together and ideally have some synergies such
as sharing common technology.
You can find some documents on
ALF at http://www.eclipse.org/alf.
Currently, ALF's security focus is on single sign-on, but eventually it will
expand to authorization and other security
aspects.
Please let me know what times
work for you and your team members for a call where we can explore the
intersection between ALF single sign-on and
Higgins.
Brian Carroll Serena
Fellow Serena (ofc) (503) 617-2436 (cell) (503) 318-2017 bcarroll@xxxxxxxxxx
**********************************************************************
This email and any files
transmitted with it are confidential and intended solely for the use of the
individual or entity to whom they are addressed.
Any unauthorized review, use, disclosure or distribution is prohibited. If
you are not the intended recipient, please contact the sender by reply
e-mail and destroy all copies of the original message.
The contents of this e-mail are intended for the
named addressee only. It contains information that may be confidential. Unless
you are the named addressee or an authorized designee, you may not copy or use
it, or disclose it to anyone else. If you received it in error please notify us
immediately and then destroy it.
|