<div dir="ltr"><div dir="ltr">Thank you both.  I was going to test it to see how ugly a message was displayed upon rejection!<input name="virtru-metadata" type="hidden" value="{"email-policy":{"state":"closed","expirationUnit":"days","disableCopyPaste":false,"disablePrint":false,"disableForwarding":false,"enableNoauth":false,"persistentProtection":false,"expandedWatermarking":false,"expires":false,"isManaged":false},"attachments":{},"compose-id":"17","compose-window":{"secure":false}}"><div><br></div><div>I will explore both of these options.</div><div><br></div><div>Regards,</div><div>Joanne</div><div><br></div><div><br></div></div><br><div class="gmail_quote" style=""><div dir="ltr" class="gmail_attr">On Wed, Jul 15, 2020 at 2:27 PM Peter Schober <<a href="mailto:peter.schober@univie.ac.at">peter.schober@univie.ac.at</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">* Brian Moon <<a href="mailto:bmoon@scu.edu" target="_blank">bmoon@scu.edu</a>> [2020-07-15 20:13]:<br>
> It sounds like what you need is a "context-check" interceptor flow<br>
<br>
This. I was cought up in answering the literal question but if service<br>
access should be disabled (and very likely no proper error message<br>
will be presented by the SP if you happily send the subject on without<br>
any usable data) the above approach obviously is much better.<br>
<br>
-peter<br>
-- <br>
For Consortium Member technical support, see <a href="https://wiki.shibboleth.net/confluence/x/coFAAg" rel="noreferrer" target="_blank">https://wiki.shibboleth.net/confluence/x/coFAAg</a><br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net" target="_blank">users-unsubscribe@shibboleth.net</a><br>
</blockquote></div></div>