<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; ">
Sam,
<div><br>
</div>
<div>
<div>
<blockquote type="cite">
<div style="font-family: Helvetica; font-size: medium; 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-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
How can I see what key is in the SAML response?</div>
</blockquote>
<div><br>
</div>
<div>The easy way is to turn the Shibboleth SP's shibd.logger to DEBUG and look at shibd.log when an assertion comes in. It will log everything in the response.</div>
<div><br>
</div>
<div>If the response is not encrypted, then you can also look at it in a browser using a tool like SAML tracer for Firefox or even a generic web console.</div>
<div><br>
</div>
<blockquote type="cite">
<div style="font-family: Helvetica; font-size: medium; 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-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
What can I check to narrow things down?</div>
</blockquote>
</div>
<br>
</div>
<div>The SP's logs will tell you exactly what went wrong. It's likely the keys, as Paul suggested, if your clocks are on.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Nate.</div>
</body>
</html>