ESOE Development Google Group

Recent spam emails

2009-09-20T05:58:54Z

Hi All,
Due to recent spam emails, I've changed the list settings so that email from
new members will be moderated. This means there will be a delay the first
time you post to either list, but will hopefully eliminate the spam we've
been seeing lately.
Regards,
Shaun

ESOE Project News - Releases, Git

2009-08-11T06:08:56Z

Hi All,
After a long period of quiet, mostly due to the shifted priorities of our
development team, I'm glad to announce that the ESOE Project is back in
active development. We have some updates:
New site, new source control
In preparation for the move to Git source control, we migrated the ESOE
Project site to Redmine ([link]) back in April. We've now moved

Re: [esoe-dev] Status of Apache SPEP for Mac OS X

2009-07-15T23:46:00Z

Hi Tim,

The site is back up, I restarted to correct a config error and it didn't
come up cleanly for some reason.

The status of the SPEP code update is that it's in progress currently. It
was delayed due to workload constraints, but is now back in active
development. I've completed a large number of changes, including the upgrade

Status of Apache SPEP for Mac OS X

2009-07-15T23:31:11Z

Hi
I was wondering what is the current status of Apache SPEP for Mac OS X Server on 64 bit Intel or PowerPC. I understand it was being upgraded to use Xerces 3.0 to be 64 bit compatible.
BTW, I am having trouble connecting to [link]
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Re: [esoe-dev] Re: ESOE Project on git?

2009-06-18T23:45:57Z

Nice one!

Re: [esoe-dev] Re: ESOE Project on git?

2009-06-18T23:37:05Z

After reading this reply, it occurred to me that it's not really unusual to
want multiple source repos, so I went digging through the Redmine issue
tracker. Somebody has already solved this problem and helpfully uploaded a
patch.
From testing this patch, it looks like we'll be able to do everything we

Re: [esoe-dev] Re: ESOE Project on git?

2009-06-18T10:36:48Z

Re branching/tagging:

What if you need to issue an urgent patch release of spepcppdaemon?
You shouldn't be forced to release all components. Separate issue
though I guess.

Re tooling:

If the tooling works better with a monolithic repository then that is
probably the way to go. It seems strange that redmine can't handle

Re: [esoe-dev] Re: ESOE Project on git?

2009-06-18T08:41:05Z

2009/6/18 Luke Daley <lda...@gmail.com>
Good point here, though certain projects are coupled tightly enough that
they should be in sync - for example:
esoecore + esoemanager + esoedeployer
spepjava + spepjavafilter
spepcpp + modspep + spepcppdaemon
Putting some effort into decoupling them might lessen the impact, but the

Re: [esoe-dev] Re: ESOE Project on git?

2009-06-18T04:58:46Z

I prefer smaller repositories.
This does cause issues with branching/tagging etc, but it may be a
good opportunity to investigate whether all of the modules need to be
bound to the same version number and release cycle.
If a monolithic repository can be avoided, I think that should be the
path.

Re: [esoe-dev] ESOE Project on git?

2009-06-18T00:41:24Z

Hi Shaun,

My experience with other large projects and Git has been the single
repository approach with top level directories for each sub component.
I've used a couple that have gone the other way. Overall there are
positives and negatives to both.

What I find does really get painful with the single repository

ESOE Project on git?

2009-06-17T11:23:39Z

Hi All,
It's come time again to revisit the idea of using git for development of the
ESOE project. A few things have changed since this was last discussed, not
the least of which is the transition to Redmine ([link]) for
managing the project.
With the revamped project site, we can now use (almost) any VCS we want. The

Re: [esoe-dev] "True Single Sign On" for Unix-based OS

2009-04-16T21:39:47Z

Hi,
It's not quite true to say that it doesn't support Unix-based OS, because it
is platform agnostic. Authentication is achieved using a Kerberos ticket
which is issued by Active Directory.
LDAP authentication, at least in the context of ESOE, is simple
username/password verification. Storing the state would just be saving your

"True Single Sign On" for Unix-based OS

2009-04-16T17:04:33Z

Hi,
Just to ensure what I understand at this moment. The cool feature like
"True Single Sign On" which automatically authenticate user after login
to Windows OS by Active Directory, is still not implemented for the
Unix-based OS authenticated using LDAP. Am I right? (I haven't tested it
yet, just read the sourcecode)

Re: [esoe-dev] Re: git, future directions

2009-03-05T08:34:55Z

If it's going to be git then the issue tracker needs to change. Take a
look at lighthouse. I am not a huge fan but it's integration with
github is tight. I don't know if there is a solution for lighthouse
that links CI builds with tickets like Jira+Bamboo but I would think
there would be something.

Re: [esoe-dev] Re: git, future directions

2009-03-05T00:49:15Z

Hudson is a good example here. Where possible I'd like to stick to
other open source solutions to support the project. We've been using
Hudson in the past with great success and flexibility.

Hudson at least seems to have pretty decent GIT support
[link]

Re: [esoe-dev] Re: git, future directions

2009-03-01T07:24:09Z

Although I see your point, I think we can find suitable substitutes that
(while not as tightly integrated as the Atlassian suite) will give us what
we need and support git natively.
This might warrant some further investigation. If it turns out that git is
too widely unsupported, we may need to stay with subversion.

Re: [esoe-dev] git, future directions

2009-02-26T22:27:38Z

No argument from me. The only thing I would be concerned about is
making sure that the tooling supports it. The project needs continuous
integration and a repository inspector, and ideally an issue tracker
linked into both of these. I have used the Atlassian tool set to do
this in the past which works well, but I don't think they are

git, future directions

2009-02-26T08:22:52Z

Hi,
I'd like to get others input on moving ESOE code bases to GIT backed
SCM. Some of the positives I believe this would bring include:
* The internal functionality Git brings to the development team is
amazing, we're using it exclusively at Intient now.
* The collaborative nature of de-centralized SCM is a much more

Re: [esoe-dev] Re: OpenSSL minimum version for saml2cpp?

2009-02-15T23:43:29Z

Hi,
Sounds good to me, I am a big fan of things being as rigorous as
possible.
Yes I am certain that there is probably a number of issues like this
floating around the doco set. Especially in relation to changes
between 0.5 and current HEAD. Would be nice to see these maintained/
updated as folks work with the code. If you need an account I can

Re: [esoe-dev] Re: OpenSSL minimum version for saml2cpp?

2009-02-15T23:18:42Z

Given that there are quite a few systems that ship with 0.9.7 then
it's probably worth stating that as the minimum requirement if possible.
The current autoconf scripts don't check for dependencies at all,
leading to compile time errors if dependencies are not satisfied. I
would like to gradually make this more rigorous so it's easier to

Re: [esoe-dev] Re: OpenSSL minimum version for saml2cpp?

2009-02-15T22:57:31Z

Hi all,

I can clarify a little here. We developed against a 0.9.8 version (the
specific version escapes me, but 0.9.8e sounds about right). We currently
have a production SPEP running on Redhat 4 which uses 0.9.7a (not sure if
this has Redhat-specific patches).. So at the least, it is API-compatible

Re: [esoe-dev] OpenSSL minimum version for saml2cpp?

2009-02-15T00:25:03Z

Hi,
I believe the minimum was 0.9.8e but the later the better.

It depends on it in a number of ways the most important being:

signature / document verification on unmarshaling
signature generation for marshaling
key verification for metadata extraction
various load/store routines for keys

OpenSSL minimum version for saml2cpp?

2009-02-14T08:14:53Z

Hey guys,

Anyone know what the minimum version of OpenSSL that ESOE supports is?

Out of interest, how is saml2cpp depending on OpenSSL?

Cheers,

LD.

Re: [esoe-dev] project update?

2009-01-29T05:07:28Z

Hi Jim,

Jim wrote:

Glad to hear it is working well.

You're correct there is a number of differences in process which are as
yet not very widely documented (we're all busy with other professional
work in the last few months). Feel free to have a crack at it if you
like, starting point is esoedeployer.

project update?

2009-01-29T04:01:28Z

Hi,

We've been using esoe for several months now in a production
environment (and it is working very well!) and I just wanted to check
the status of the next release of ESOE and if there is anything that I
could do to speed up the process.

I guess a good question would be how to install and setup the ESOE

ESOE Project Update

2008-08-28T05:30:01Z

Hi,
So it's been a while since any of the core dev team made much public comment
about whats been going, those watching SVN are aware but I thought it would
be useful to make things a little more transparent.
Firstly we have a new web presence, a little cleaner then before and
highlights facts about the project that ohloh are kindly assembling from our

Re: SVN

2008-07-29T00:40:51Z

Hi,
Barring any DNS propagation issues this move has been completed.

SVN is now available in read form at:
[link] (note this URL is different
from the previous location)

This repository has been upgraded to SVN 1.5 so you will need to drop
and reload any previous checkouts and possibly upgrade to the most

SVN

2008-07-25T14:09:11Z

Hi,
ESOE SVN is currently being migrated to a new server and at the same
time SVN 1.5

At this stage the move is probably going to take a few days so access
from the world will be non existent until early next week.

If you have something urgent let us know.

thanks
Bradley

Apache SPEP Beta 2 (0.5.2) released

2008-05-23T00:23:25Z

Hi everyone,
Following the release of Apache SPEP 0.5 recently, there have been a few bug
fixes, the most notable being the spepd startup error (
[link]). As such, I have released a bug
fix release. 0.5.1 was an internal testing release so we're at version 0.5.2
now.

Apache SPEP Beta 2 (0.5) released

2008-04-30T06:05:38Z

Hi everyone,
I am pleased to announce the Beta 2 (0.5) release of the Apache SPEP
libraries. This release contains a number of fixes for bugs and minor
usability issues, most notably:
- SPEP daemon fails gracefully upon a configuration error.
- SPEP daemon will now generate a PID file if requested.
- Solved some cross platform portability issues

ESOE Virtual Machine

2008-04-08T01:43:48Z

Hi,
Recently we released a 0.7.0 snapshot of ESOE. To assist users in seeing
how this new version is deployed and also to allow people to test ESOE
without needing to do a large install we are please to now offer a Linux
based VM which is fully configured to act as the central ESOE server.
You can download from the following location:

ESOE 0.7.0 (unoffical Beta 3)

2008-03-31T04:30:32Z

Hi,
We'd like to announce the binary availability of ESOE 0.7.0 at:
[link]
This is what we would normally have shipped as the Beta 3 release though
we aren't going to cut a Beta 3 at this point and will instead move to
1.0 as the next "official" version released. 0.7.0 is in production

GSOC 2008

2008-03-10T07:51:14Z

Hi All,
We have now entered an application for the Google Summer of Code 2008
and have an ideas page up at
[link]
This page will be updated when we know the outcome of our application as
a mentor.
In the meantime the core development team would love to hear any ideas

Apache SPEP Beta 1 (0.4) released

2008-02-18T00:55:42Z

Hi everyone,
I am pleased to announce the Beta 1 (0.4) release of the Apache SPEP
libraries. This release contains bug fixes and some significant
improvements to the configuration process.
We highly recommend that anyone upgrading from an earlier release
rewrite their configuration based on the new spep.conf.default

Apache SPEP Alpha 3 (0.3) released

2007-11-12T01:38:21Z

Hi everyone,
I am pleased to announce the Alpha 3 (0.3) release of the Apache SPEP
libraries. This release contains many bug fixes and some significant
work to the web services code.
Anyone out there wishing to upgrade will need to make a minor change
to their ESOE environment, detailed on the Apache SPEP wiki page at:

ESOE Beta 2 released

2007-11-12T01:05:42Z

Hi,
I am pleased to announce the availability of ESOE Beta 2.
Changes in this addition include several bug fixes, updates to the
splash screen between services and the ESOE on initial authenticaton and
support for the back/forward button to be used correctly in browsers.
At this point we also intend to roll out a new version of the Apache

Information for Beta 2

2007-10-09T02:13:34Z

Hi All,
Over the past few weeks we've received a number of pieces of feedback on
Beta 1 testing. As a result of this we've identified and corrected
several issues.
Additionally with relation to Java SPEP software we have made a small
architectural change. Previously this software required a large number

C++ SPEP Alpha 1 released

2007-09-20T11:02:20Z

Hi everyone,
I am pleased to announce the Alpha 1 release of the C++ SPEP code.
This release includes our SAML2 library for C++, as well as the SPEP daemon
and an Apache module. Full deployment instructions are available on the ESOE
Users wiki, which I encourage you to visit.
Links for download are currently available at

ESOE Beta 1 Release

2007-09-14T11:44:51Z

Hello All,
I am extremely pleased to announce the Beta 1 release of the Enterprise
Sign On Engine.
This is a significant milestone with many issues which were raised as a
result of the Alpha releases and testing being resolved and rolled into
this release.
One of the really important new things for Java is that we now natively

ESOE Beta 1 Schedule

2007-09-10T05:48:56Z

Hi All,
Just a heads up that we expect to release Beta 1 of the ESOE this coming
Friday 14/9
A full list of corrected issues and new features (and there is a LOT of
both) are available in Jira.
regards,
Bradley

Re: [esoe-dev] Re: SAML2 questions for thesis

2007-07-26T08:26:34Z

Hello,
Sorry this took a little longer then expected retrieving the jars from
backup was a bit of a pain.
The good news is that everything is available in the Intient Ivy
repository at [link]
Additionally I have written the first of several developers documents

Re: [esoe-dev] Re: SAML2 questions for thesis

2007-07-24T03:59:06Z

Hi,
I've had some delay with getting the alpha 3 binaries up into ivy. After
I have moved house seems like I have a misbehaving HDD. I will need to
pull the backup copies which is going to take a while longer.
I will let you know when its up in the ivy rep.
Bradley

Re: [esoe-dev] Re: SAML2 questions for thesis

2007-07-23T06:11:23Z

Hello,
I am currently on a short holiday and will be returning to full time
work on the 30th so responses from me will be slower then normal, though
as you've already seen Shaun and Andre are still around to answer queries.
Building the jar from the trunk is actually very easy once you have ivy
and ant configured correctly, I am currently writing a document on this

Re: SAML2 questions for thesis

2007-07-23T02:41:42Z

Hi Shaun,
Thank you for your quick response.
We have been browsing the source code for saml2java and believe it
would be great for our thesis.
But we were unsuccessful in building the jar (from trunk). Where do we
download just the saml2java jar from? (There is no link on your wiki
downloads page).
Also we are a bit confused about the

Re: SAML2 questions for thesis

2007-07-23T02:04:30Z

Hi,
As the saml2java library is a generic implementation of SAML 2.0, I
would suggest that it will do what you need. We are currently using it
to create documents to send over web service calls and have had a lot
of success.
I would encourage you to browse the API for saml2java, to see what you
can do with it. I'm not sure that we have library documentation online

SAML2 questions for thesis

2007-07-22T06:05:29Z

Hi,
We are currently doing a thesis at UNSW which requires user
authentication across domains upon web service calls. We have been
investigating SAML2 to achieve federation using persistent identifiers
and came across your ESOE project.
Is it possible to use your saml2java library to achieve this? If so,

Ivy Binaries for Alpha 3

2007-07-12T04:33:25Z

Hi,
I've been asked a couple of times where the binaries for alpha 3 are
with regards to ivy resolution. The short answer is I didn't have time
to upload them before i had to jump a plane to Cairns for a conference I
am at.
Fear not however the binaries are ready and waiting to go on my return
Friday.

ESOE Alpha 3 released

2007-07-09T14:42:24Z

Hi All,
We have just released Alpha 3 of the ESOE.
Many bug fixes have gone into this release specifically relating to
MySQL deployments.
New features for this release are integrators for Confluence, Jira and
Blackboard.
As always links for downloads are available at [link]
regards,

ESOE Alpha 2 released

2007-07-02T15:23:37Z

Hi All,
We have just released Alpha 2 of the ESOE.
Many bug fixes have gone into this release along with more
documentation, though there is still more to come.
New features for this release are the first official releases of the
shibboleth and openID delegators for ESOE.
We've updated the community web portal at

Fisheye Available

2007-05-22T05:59:12Z

Hi All,
We're happy to announce that Fisheye has been made available for the
ESOE development community at [link]
Thanks to Cenqua for their generous open source license. More tools will
be launching over the next few days.
regards,
Bradley