Shibboleth Developers

I agree that it would be good to comment out the 
edPersonScopedAffiliation attribute definition in resolver.xml.  
This would, as Scott pointed out, be most consistent with the way 
origin.properties is formatted. (ie: example values are commented 
out if they must be changed to work for people)

-Walter

P.S.  I am out today and tomorrow, but will try to keep up with 
email.  

Quoting Scott Cantor 
<>:

> > One suggestion, tho, that may well be doable -- in the deploy
> guide
> > create a checklist -- a list of items (which are links) of the
> tasks
> > which have to be addressed when deploying an origin or target.
> > Hopefully, the list wouldn't be too long, but would be complete
> (eg
> > would include "edit resolver.xml to add appropriate scope
> value").
> 
> +1.
> 
> I'd much rather do this than start making wholesale changes. I
> don't object to just commenting out the scoped attribute as Bob
> suggested, since the origin properties file already has required
> entries that are commented out anyway.
> 
> And yes, it's a fairly short list. I have much more trouble doing
> updates because I'm updating 0.8 origins to 1.0 and trying to
> maintain config files. Just setting one up is easy.
> 
> -- 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--
> 


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

    http://archives.internet2.edu/

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