<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Good Afternoon!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We are currently running IDPv3.3.3 and have Duo/MFA configured to be enforced by default on all SPs. We’re attempting to troubleshoot an issue with an SP regarding how the page is presented after successful SSO login. The SP’s page displays
as a mobile view in a desktop browser on the first login, but will direct to the desktop view on subsequent logins once the SAML and Duo cookies are in place. The vendor suspects that since the Duo auth page appears to be in a mobile view (I’m not actually
sure if it is or not), that state is being carried over to the SP application through the browser or the cookie which is causing the display issue. I don’t suspect this to be the case, but in an effort to cross that possibility off the list, we would like
to temporarily disable MFA for this SP specifically. If it’s not possible we’ll have to migrate the config to our Dev environment and shut off Duo globally, which is potentially more work. I’m hoping there is a relying-party bean that may be simpler.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Can MFA be bypassed for a single SP?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">--<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Jack Garmer<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Linux Systems Administrator<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">James Madison University<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">o. 540-568-4235<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>