AuthnContextClassRef from SSP SP seeming to be ignored

Brent Putman putmanb at georgetown.edu
Wed Jan 11 20:23:16 EST 2017



On 1/11/17 8:07 PM, Cantor, Scott wrote:
> On 1/11/17, 7:56 PM, "users on behalf of Brent Putman" <users-bounces at shibboleth.net on behalf of putmanb at georgetown.edu> wrote:
>
>> But I'm not clear how we'd support user-configuration of the "trigger" for any given instance of logging.
> Probably the same way I did the timers, with a scriptable trigger using a context to store the rules. 

I never looked at that in detail.  I guess context data can drive it,
but then the question is: what data...

Within the action, one does have access to all the SWF RequestContext
stuff.  So I guess theoretically many things are possible from that,
like using the current flow ID (from the active FlowDefinition), and
current state ID (from the current StateDefinition), as well as of
course all the various -Scope data. 

So maybe outside-in could be triggers based on (flow ID + state ID),
injected either into context tree or as flow/conversation scope data.

Haven't tried it, but that might be generally useful for other action
trigger-y things as well.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170111/e21a1052/attachment.html>


More information about the users mailing list