<div dir="ltr">The default on new-installs should definitely be on, but for upgrades, I'd rather see it behave as v2 does today (no consent).<div><br>Dave</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 17, 2014 at 12:13 PM, Cantor, Scott <span dir="ltr"><<a href="mailto:cantor.2@osu.edu" target="_blank">cantor.2@osu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 11/17/14, 7:07 PM, "David Langenberg" <<a href="mailto:davel@uchicago.edu">davel@uchicago.edu</a>> wrote:<br>
<br>
>That's true, but at the same time, turning on consent (at least here)<br>
>will take an act of a committee and involve a bunch of sign-offs for<br>
>usability, testing, etc. Upgrading to IdPv3 without turning on consent<br>
>just requires sending a FYI to my announce list & a 5 minute<br>
>change-advisory call.<br>
<br>
</span>Sure, but I'm not saying you couldn't turn it off with a switch, I'm just<br>
wondering what the default should be with an eye on the community as a<br>
whole given that unfortunately or not most places just run a lot of very<br>
vanilla stuff without much regard for why.<br>
<div class="HOEnZb"><div class="h5"><br>
-- Scott<br>
<br>
--<br>
To unsubscribe from this list send an email to <a href="mailto:dev-unsubscribe@shibboleth.net">dev-unsubscribe@shibboleth.net</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">David Langenberg<div>Identity & Access Management</div><div>The University of Chicago</div></div>
</div>