Subject: Grouper Developers Forum
- From: "Tom Scavo" <>
- To: "Tom Zeller" <>
- Cc: "Grouper Dev" <>
- Subject: Re: [grouper-dev] grouper extenders ?
- Date: Fri, 28 Mar 2008 09:31:14 -0400
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=WQeYd87mril3ALNjmD+Dle0FvUuS+xGmzOq+bKIkZUid2EcnILZ70zaZz/at+G2Xp+e8g82w34F4lmI/HBKmqtLc/8JEY/eBXWGCjAntjDQekn3sb1y5lE9fKvidYVHQtfatkqzHV3Bejqfv0WUBufo67KSz1s2DS8hORowEhUQ=
Well, in that case, I wrote a fairly complex extension for the Shib
1.3 IdP a couple of years ago, and that worked fine for the most part.
A point release of the 1.3 IdP broke the extension but I never
bothered to go back and fix it since we want to replace it altogether
with a similar extension based on Shib 2.0 IdP.
The bottom line (for me) is: the Shib extension framework is a good
way to package a plugin, but obviously once you put the framework out
there, you have to apply strict change management techniques so that
you don't break third-party extensions.
Speaking of which, third-party extensions imply a public API. You
need make it clear to your users which parts of the API are public and
which are not. Again of course the public API components require
strict change management.
Sorry if I've mentioned things that you've already thought through.
If there's something specific you'd like to know, just ask and I'll
see what I can do.
On Fri, Mar 28, 2008 at 8:58 AM, Tom Zeller
> >> Have you written an extension (are you an extender) ? Do you have
> >> comments regarding the 'ext' framework ?
> > Which extension framework are you referring to? Grouper? Shibboleth?
> > Something else?
> Grouper, whose extension framework is based on Shib's - hence comments
> on either seem appropriate.
- grouper extenders ?, Tom Zeller, 03/27/2008
Archive powered by MHonArc 2.6.16.