On 09/21/2011 02:56 PM, Jasha Joachimsthal wrote:
We've configured Rave to use our (internal) Shibboleth for authentication
using [1] as example.
The configuration is not something we can add to the demo portal to work out
of the box but it can be documented. Are there any objections if I would add
the (slightly modified) java code to the Rave portal?
I'd like to see Shibboleth *supported* by Rave.
If we add code for this in "core" Rave, we should be able to use and demonstrate
it, so I'd want "full" (even if only limited) support ;)
Otherwise, it will not be possible by the Rave team itself to ensure and
validate proper operation and behavior and actually could then become more of a
problem than a benefit.
If however you only can provide a "half-way" solution, I think it might be
better to keep it outside "core" Rave, e.g. only as exemplar code/configuration.
Can you enlighten us why you can't provide a complete functionality?
Is it just too much work, or too dependent on the custom environment. In the
latter case, what would be effort to generalize your solution which would work
both for Rave and in your own environment?
Ate
[1] https://manager.aaf.edu.au/wiki/display/mgtpac/Home
Jasha Joachimsthal
Europe - Amsterdam - Oosteinde 11, 1017 WT Amsterdam - +31(0)20 522 4466
US - Boston - 1 Broadway, Cambridge, MA 02142 - +1 877 414 4776 (toll free)
www.onehippo.com
