<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">If you get through a replay error, but a subsequent exchange with the IdP does the same thing, you'll at least sometimes end up with a flow execution error because the second request will hit after
the first one has advanced the flow state past the point that the second one would work. It's not a replay exactly but the effect is the same.</span></p>
<p><br>
</p>
<p>I think we get more expirations than replays by an order of magnitude, but I'll have to turn the logging back on to know.</p>
<p><br>
</p>
<p><span style="font-family:Calibri,Arial,Helvetica,sans-serif,EmojiFont,"Apple Color Emoji","Segoe UI Emoji",NotoColorEmoji,"Segoe UI Symbol","Android Emoji",EmojiSymbols; font-size:16px">The concerns I'm reading seem to apply almost exclusively to replays.
</span>Do you have reason to believe that disabling expiration checking alone would incur death by Webflow?</p>
<p><br>
</p>
<p>I don't think that addresses Paul's satellite users, but it would address at least some of my cell phone users.</p>
<p></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 4:52:13 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, 7:19 PM, "users on behalf of Klingenstein, Nate" <users-bounces@shibboleth.net on behalf of nklingenstein@calstate.edu> wrote:<br>
<br>
> That was my hunch based on prior responses and conversations. This is much more at the "try it and see what happens" phase<br>
> than anywhere else.<br>
<br>
Testing it is probably fine, but yeah, I basically after a few minutes thinking can assure you that it probably won't work. If you get through a replay error, but a subsequent exchange with the IdP does the same thing, you'll at least sometimes end up with
a flow execution error because the second request will hit after the first one has advanced the flow state past the point that the second one would work. It's not a replay exactly but the effect is the same.<br>
<br>
> I'll see if I can reasonably test something, realizing full well that this is likely to result in incidental unexpected behavior by<br>
> Webflow that would otherwise get trapped and caught.<br>
<br>
It's not about making it work badly. It just fails, albeit with a different error at a different point.<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>