<div><div style>Scott,</div><div style><br></div><div style>My take away from this is that this setup *should* work ... I'll work with the admin to see what is causing the issue.</div><div style><br></div><div style>My understanding is that the NU admin has this setup working with other SPs.</div>
<div style><br></div><div style>Thanks.</div></div><br clear="all"><br clear="all">Mike Basil<br>312.961.7798<br><br>
<br>
<br><br><div class="gmail_quote">On Mon, Apr 2, 2012 at 15:48, Cantor, Scott <span dir="ltr"><<a href="mailto:cantor.2@osu.edu">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">
<div class="im">> We are using browser post. The URL that is generating the SAML 1 request<br>
> looks identical minus a state ID (noted below) ... so I don't think it is a<br>
> corrupted request. The request lengths are less than 600 characters too, so<br>
> there isn't anything like that in play.<br>
<br>
</div>Doesn't seem to be.<br>
<div class="im"><br>
> Plus, the assertion states the Audience correctly in both cases.<br>
<br>
</div>No chance of this happening then, so...no idea. Time to start tracing code and logs.<br>
<div class="im"><br>
> Could there be Attribute Release Policies in play (that I should have the<br>
> admin check)?<br>
<br>
</div>No, policies in 1.3 know nothing about the location of the client.<br>
<div class="HOEnZb"><div class="h5"><br>
-- Scott<br>
<br>
--<br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a><br>
</div></div></blockquote></div><br>