<div dir="ltr">IMO, after upgrading, I'd like it to work just as it does now. If I need new features (like consent) then I don't see it as being a problem to require me to update my config to the new formats.<div><br>Dave</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 17, 2014 at 10:34 AM, 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">Should we be attempting to enable the attribute-release intercept on<br>
upgrades? Right now it isn't possible to enable those flows with the<br>
legacy config you get after an upgrade, so that's probably a major block<br>
to a lot of sites enabling the consent feature.<br>
<br>
I could probably add enough schema to the legacy syntax to support turning<br>
it on, or we could turn it on by default internally and people that wanted<br>
to turn it off could use a brute force approach and attach a False<br>
condition to the flow.<br>
<span class="HOEnZb"><font color="#888888"><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>
</font></span></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>