<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body dir="auto">
<div><br>
</div>
<div>On May 26, 2014, at 7:56 AM, "TISSOT Jacques Joseph" <<a href="mailto:jacques.tissot2@unifr.ch">jacques.tissot2@unifr.ch</a>> wrote:<br>
</div>
<blockquote type="cite">
<div class="WordSection1"><br>
<p class="MsoNormal"><font size="2" face="Calibri"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font size="2" face="Calibri"><span lang="EN-US" style="font-size:11.0pt">Politics aside, is it a way to handle a CAS server fail by connecting back to the ShibUserPassAuth method (without reconfigure and restart the IDP)?</span></font></p>
</div>
</blockquote>
<div><br>
</div>
<div>A possible better approach would be to create a fully HA login tier to avoid the failure scenario altogether.</div>
<div><br>
</div>
<div>If you are insistent on the "fall-back" login handler option. It sounds like your best option is to construct your own LoginHandler that would handle the absence of CAS and move on to local UserPass login.</div>
<div><br>
</div>
<div>- sent from mobile</div>
<style><!--
/* Font Definitions */
@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:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</body>
</html>