<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Yes, Since we never had SAML2 ACS so far on SP side, we are assuming there were no SAML2 only IDP that we were interacting with currently. So our assumption was that nothing will break as of today even if we did not update the metadata. But we started adding the SAML2 ACS points in metadata's anyway so we should be safe I guess. <div><br></div><div>Thanks</div><div>Jayashree</div><div><br></div><div><br><div><br></div><div><br><br><div><div id="SkyDrivePlaceholder"></div>> From: cantor.2@osu.edu<br>> To: users@shibboleth.net<br>> Subject: Re: Addition of SAML2 support for SP<br>> Date: Thu, 8 Nov 2012 20:07:10 +0000<br>> <br>> On 11/8/12 2:56 PM, "Jayashree Ravi" <jravi123@hotmail.com> wrote:<br>> <br>> >Thanks Ian, We started the process of updating our metadata in other<br>> >federations as well to include the SAML2 endpoints just to be on the<br>> >safer side.<br>> <br>> At this point, any IdP in one of those federations that is SAML 2 only<br>> will simply break. You can't deploy SAML 2 anywhere until your metadata is<br>> available in all the systems that you may interact with via SAML 2, and<br>> that means waiting on the SAML 2 enablement until that's done (or<br>> accepting that it will break for those IdPs).<br>> <br>> -- Scott<br>> <br>> <br>> --<br>> To unsubscribe from this list send an email to users-unsubscribe@shibboleth.net<br></div></div></div> </div></body>
</html>