<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div>I find that a bit confusing. Initially you were saying it'd be caused by SP behavior, but then then that no settings would cause that behavior. Do you mean Shibboleth SP has no settings that might cause that in general? I suppose I can't rule out that
they have since switched away from Shibboleth SP.</div>
<div><br>
</div>
<div>That said, have you seen this sort of behavior in any SPs you've worked with in general? And if so, is there any setting on the IDP side that might coax it into behaving better? At this point we're trying to see what might be causing this behavior in general
but we're hitting dead ends.</div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<div>Brandon McKean</div>
<div><br>
</div>
<div>On Tue, 2015-08-04 at 15:24 +0000, Cantor, Scott wrote:</div>
<blockquote type="cite">
<pre>On 8/4/15, 11:08 AM, "users on behalf of McKean, Brandon Scott - mckeanbs" <<a href="mailto:users-bounces@shibboleth.net">users-bounces@shibboleth.net</a> on behalf of <a href="mailto:mckeanbs@jmu.edu">mckeanbs@jmu.edu</a>> wrote:
<blockquote type="cite">
I had a follow up on this one. It looks like a few years ago, someone from this SP posted on this mailing list, indicating they are using Shibboleth SP or at least did at some point.
Is there any particular setting(s) in that where double logins might be caused from clients going from IDP v2 to v3?
</blockquote>
No.
-- Scott
</pre>
</blockquote>
</body>
</html>