<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 17, 2014 at 12:02 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:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">On 11/17/14, 7:01 PM, "David Langenberg" <<a href="mailto:davel@uchicago.edu">davel@uchicago.edu</a>> wrote:<br>
<br>
>IMO, after upgrading, I'd like it to work just as it does now. If I need<br>
>new features (like consent) then I don't see it as being a problem to<br>
>require me to update my config to the new formats.<br>
<br>
</span>I think that's all true, but it has implications on the actual impact of<br>
prividing consent. As in, it will get very little use aside from new<br>
installs, so that dilutes the impact.<br></blockquote><div><br></div>That's true, but at the same time, turning on consent (at least here) will take an act of a committee and involve a bunch of sign-offs for usability, testing, etc. Upgrading to IdPv3 without turning on consent just requires sending a FYI to my announce list & a 5 minute change-advisory call.<div><br></div><div>Dave</div><div><br></div><div><br></div></div>-- <br><div class="gmail_signature">David Langenberg<div>Identity & Access Management</div><div>The University of Chicago</div></div>
</div></div>