<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>Bryan,</div>
<div><br>
</div>
<div>
<blockquote type="cite">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif; ">
<div>
<div>I swear I just some recent posts regarding filtering access to Sps at the Idp. Ie the SP thinks that authentication equals authorization so it is incumbent on the Idp to deny access.</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>You're probably thinking about the thread from my recent post to the dev@ list. June 4 MDT, "<span style="font-size: 12px; ">Stopping users for insufficient attributes at the IdP in v3".</span></div>
<br>
<blockquote type="cite">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif; ">
<div>
<div>In our case we a talking Box. We only want current staff/students to get accounts via Box "auto-provisoning". Apparently Box can't/won't use eduPerson affiliation to make the decision.</div>
<div><br>
</div>
<div>Anyway we need to reject logins where the user is not staff/affiliate. Does that make sense?</div>
<div><br>
</div>
<div>Looking for guidance.</div>
</div>
</div>
</blockquote>
<br>
</div>
<div>I think the responses in that thread will guide you towards today's options, tomorrow's options, and a conversation to continue with SP's. A more precise question will help if you are left wondering anything.</div>
<div><br>
</div>
<div>Hope this helps,</div>
<div>Nate.</div>
<br>
</body>
</html>