Shibboleth Developers

["RL 'Bob' Morgan" <>]

Thinking about this some more, it's dumb to force InCommon participants to
config a bunch of stuff we could do for them.  Maybe the right thing is to
have a distro labelled "pre-configured for InCommon pilot", with audience
and AAP and stuff as it should be, and another "for general use" that is
neutral.  And maybe it's OK if we deliver the InCommon one first and the
general one a little later.  Obviously the requirement longer-term is to
be able to deliver/install fed-specific config info without it being
bundled with the full package.

 - RL "Bob"

On Tue, 10 Jun 2003, Scott Cantor wrote:

> > > Do we pull the pilot URI?
> >
> > ... but we would tell InCommon participants to configure it
> > back in, right?
>
> Yes, I'd assume so.
>
> > My perhaps unrealistically extreme position (and maybe this
> > is the wrong time to wave this flag, so shoot me) is that the
> > Shib software package shouldn't when taken out of the box
> > have any InCommon-oriented config items in it.  I guess that
> > this is a more, uh, interesting question when it comes to
> > attribute stuff (basically eduPerson), which is sprinkled all
> > about.  But for example the provided AAP.xml is, I would say,
> > InCommon-specific.
>
> In the entitlement rule, I s'pose it is. I could comment it out, but I 
> wanted to at least provide an example. I guess I could dummy
> it up a bit more.
>
> -- Scott
>
>


------------------------------------------------------mace-shib-design-+
For list utilities, archives, subscribe, unsubscribe, etc. please visit the
ListProc web interface at 

    http://archives.internet2.edu/

------------------------------------------------------mace-shib-design--