<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Arial,Helvetica,sans-serif">
<p>> <span style="color:rgb(33,33,33); font-size:13.3333px">But since the stored URL would involve the IdP, and not any host that anybody would actually want to visit, I can't imagine why somebody would happen into doing it. i.e. The URL you start typing is
wiki.shibboleth.net, not the IdP it sent you to.</span></p>
<p><span style="color:rgb(33,33,33); font-size:13.3333px"><br>
</span></p>
<p><span style="color:rgb(33,33,33); font-size:13.3333px">Failed HTTP requests and resorting to the back button if they get a "this page couldn't load" at some point. </span><span style="color:rgb(33,33,33); font-size:13.3333px">It's specifically occurring
only on devices using cellular networks, some mobile providers have spotty coverage here, and our users expect to be able to login without human interaction in most situations. I think that confluence of factors to be why I hear this so much now.</span></p>
<p><span style="color:rgb(33,33,33); font-size:13.3333px"><br>
</span></p>
<p><span style="color:rgb(33,33,33); font-size:13.3333px">Why do people apparently get stuck consistently on this particular check? I can think of several reasons, but initial DNS resolution of the IdP combined with traffic prioritization by the mobile carriers
smells very suspicious to me.</span></p>
<p><span style="color:rgb(33,33,33); font-size:13.3333px"><br>
</span></p>
<p><span style="color:rgb(33,33,33); font-size:13.3333px"><span style="color:rgb(33,33,33); font-family:Calibri,Arial,Helvetica,sans-serif,EmojiFont,"Apple Color Emoji","Segoe UI Emoji",NotoColorEmoji,"Segoe UI Symbol","Android Emoji",EmojiSymbols; font-size:13.3333px">As
you point out, that would equally torpedo most of the hops in the transaction, though, so I don't think there's a get-out-of-jail-free card here. Telling users to start again is probably the best I can do. I'll dust off the blink tag.</span><br>
</span></p>
<p><span style="color:rgb(33,33,33); font-size:13.3333px"></span></p>
<p><span style="color:rgb(33,33,33); font-size:13.3333px"></span></p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> users <users-bounces@shibboleth.net> on behalf of Cantor, Scott <cantor.2@osu.edu><br>
<b>Sent:</b> Wednesday, April 19, 2017 5:43:58 PM<br>
<b>To:</b> Shib Users<br>
<b>Subject:</b> Re: "Replay detected of message" causes</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">On 4/19/17, 8:29 PM, "users on behalf of Nate Klingenstein" <users-bounces@shibboleth.net on behalf of ndk@sudonym.me> wrote:<br>
<br>
> I have no idea what these people are doing or not doing, but I think<br>
> this is totally plausible on a network with high latency, intermittent<br>
> availability, mystery clients, and browsers that remember URLs. It's<br>
> sporadic, as mentioned, so I'll press the affected users for more<br>
> details on exactly when they're experiencing this.<br>
<br>
Clicking on stored URLs would be plausible and if it didn't involve latency issues, that probably would be fixable without the checks.<br>
<br>
But since the stored URL would involve the IdP, and not any host that anybody would actually want to visit, I can't imagine why somebody would happen into doing it. i.e. The URL you start typing is wiki.shibboleth.net, not the IdP it sent you to.<br>
<br>
-- Scott<br>
<br>
<br>
-- <br>
To unsubscribe from this list send an email to users-unsubscribe@shibboleth.net<br>
</div>
</span></font>
</body>
</html>