<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
They wrote their own SAML 2.0 implementation, for what it's worth, and they use it with many customers already. I have no idea whether they already had code to sign AuthnRequests implemented and working, so it's not a bad question to ask them.
<div><br>
<div>
<div>On Jun 6, 2013, at 0:17 , Cantor, Scott wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">If
it's a key/sig problem, it's tougher, because the key's not in the<br>
message. The only thing you can do is say that it's invalid, and then it's<br>
on them to debug it. It could be that their code is simply broken unless<br>
they have evidence it works with another known correct implementation.<br>
</span></blockquote>
</div>
<br>
</div>
</body>
</html>