AuthnContextClassRef from SSP SP seeming to be ignored

[Brent Putman]

On 1/11/17 7:44 PM, Cantor, Scott wrote:
>
> We could likely do this with JSON via Jackson pretty auto-magically. I used it for the metrics and it seemed to be pretty robust (plus has the options to extend it).

Yeah, I did think of Jackson.  Even if one doesn't need JSON, Jackson
is pretty good at serializing anything, and is highly configurable.
Since we now already have it in the dependency set, that might be the
path of least resistance.

>
>
> I guess it's not readily clear how we could do it outside-in without requiring flow editing. I suppose we could hook in more logic inside the pre/post logic of the profile action base class.

Yeah, the model right now is you insert into the flow at the point(s)
where you want it.  It's oriented to developers, not end-users. 

I guess the same code could be refactored to be available to every
action via the base class.  But I'm not clear how we'd support
user-configuration of the "trigger" for any given instance of logging. 
If each profile action impl class were only used once anywhere, then I
guess you could do it with a simple list of the class names that should
log.  But that's not generally true.  And anything that contextualizes
it for specific actions in specific flows seems like it would have to
be local to the flow definition. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170111/cb4bfcbd/attachment.html>