Adding a context-check on the fly

[Andrew Morgan]

On Tue, 14 Feb 2017, Cantor, Scott wrote:

> On 2/13/17, 7:56 PM, "users on behalf of Andrew Morgan" <users-bounces at shibboleth.net on behalf of morgan at orst.edu> wrote:
>
>> Is there a way to add a new  one and reload a service to pick up the change?
>
> Adding flows or changing flows is not dynamic. The only thing that might 
> be reloadable is if it's possible to externalize a scriplet in a file, 
> and I'm not sure that I've ever established either way if it's possible 
> to edit those on the fly or not. I think not, but I can't rule it out. I 
> suspect we can introduce a resource layer in between the script engine 
> and the source of the script to make those dynamic, but I would bet that 
> we can't ever make flows work that way.

Okay, that was my guess too.

If we are satisfied with a common error message ("Access Denied - blah 
blah"), is there a reasonable way to handle multiple SPs?

We could abstract the eligibility information into an attribute named 
"<service>-eligible", but I'm not sure how to link that to an SP (by 
entityID?)...  Is this a common pattern with a common solution?

Thanks,
 	Andy