<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=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<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:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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.hoenzb
{mso-style-name:hoenzb;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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="blue" vlink="purple">
<div class="WordSection1">
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D">Eric:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">></span>> Another potential use case which is probably infrequent in Shib<br>
<span style="color:#1F497D">></span>> deployments, but seems to be generally on an uptick in other areas is<br>
<span style="color:#1F497D">></span>> implementing least privilege/privilege escalation management. If done<br>
<span style="color:#1F497D">></span>> during the IdP authentication, the authentication process could allow you to<br>
<span style="color:#1F497D">></span>> specify the roles that you need for your access; in such a case reauthing at<br>
<span style="color:#1F497D">></span>> the IdP could end up returning different attributes depending on how you<br>
<span style="color:#1F497D">></span>> specify your need.<br>
<br>
<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Samuele:<o:p></o:p></span></p>
<p class="MsoNormal">>Yes, basically this. For instance, a /user location could require a user-pwd authn
<o:p></o:p></p>
<p class="MsoNormal">>because it only allows to check data, whereas an /updateInfo (or /admin) location
<o:p></o:p></p>
<p class="MsoNormal">>may require otp as it allows to edit and data. In my case, currently the returned
<o:p></o:p></p>
<p class="MsoNormal">>attribute set may be the same, and I'm doing access control by checking the
<o:p></o:p></p>
<p class="MsoNormal">>authentication method.<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Scott:</span><br>
<span style="color:#1F497D">></span>Haven't seen that so much as just step-up, requesting either a new login as presence
<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">></span>proof or adding the second factor for specific functions. That obviously also fits within
<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">></span>the OP's scenario, at least in theory. Getting that in place out of the box was the main
<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">></span>focus of the 3.3 work.<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Because I’ve been looking at PAM solutions recently (feel free to send me your comments on specific PAM solutions off list!) I was thinking of a finer-grained
access management approach, but in the particular case you (Samuele) describe, it sounds like what you are doing is “step up” authentication (requiring a stronger authentication event), even though it could conceptually be extended into a more PAM-like approach.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">(And again I’m largely using this response as an excuse to troll for information/experiences related to PAM solutions…)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">--- Eric<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>