centralized DS - contributions?

[Vladimir Mencl]

Hi,

We (the Tuakiri federation in New Zealand) are running our own version 
of the CDS, forked off at version 1.1.2.

At that point, we had requirements for some features that were not 
available in the CDS then.

The main feature we needed was a way for users to permanently store the 
IdP selection, so that next time, they get redirected without having to 
interact with the DS interface again.

Plus a number of other features - the main features in our version are:

* redirectMe checkbox (as per above)
* setting a default federation (automatically select one federation 
instead of "All sites" in a MultiFed setup).  Useful when one federation 
is the "home federation.

* logging a session log (for collecting federation usage statistics)

* configurable metadata refresh intervals (pass interval+fraction 
parameters to MetadataProvider)

* support for putting multiple DS instances behind an F5 load-balancer - 
status URL controlled by presence of a local file + passing 
X-Forwarded-For headers into session logs.

* plus a number of minor fixes which might have been duplicating what 
happened in CDS trunk in the meantime.

When doing the first batch of work on our fork, I was meaning to 
contribute this back.... but it took me an awfully long amount of time, 
apologies about that.

Now that I finally got to it - would you be interested in merging any of 
these features into the CDS core version?

I understand I would most likely be maintaining our own fork anyway, but 
just wondering how much of this can be shared with the main CDS...


Cheers,
Vlad

-- 
Vladimir Mencl, Ph.D.
E-Research Services and Systems Consultant
BlueFern Computing Services
University of Canterbury
Private Bag 4800
Christchurch 8140
New Zealand

http://www.bluefern.canterbury.ac.nz
mailto:vladimir.mencl at canterbury.ac.nz
Phone: +64 3 364 3012
Mobile: +64 21 997 352
Fax: +64 3 364 3002