AuthenticationResult/FlowId for SPSession
Cantor, Scott
cantor.2 at osu.edu
Mon Sep 15 10:53:01 EDT 2014
On 9/15/14, 10:30 AM, "Marvin Addison" <marvin.addison at gmail.com> wrote:
>
>>Honestly, the flow ID there was sort of a tacked on thing, I put it there
>> when I created the SPSession interface thinking it might be useful later
>
>At first glance I thought it was there to support multi-factor use
>cases, but on further consideration it seems like it's only useful for
>auditing or reporting.
Yes, and auditing is really handled up front by the audit log anyway.
>That's the approach I took for the moment:
>
>session.getAuthenticationResults().iterator().next().getAuthenticationFlow
>Id()
>
>That solution makes me uncomfortable because I'm just pulling the
>first one of an unordered collection. In the face of multiple
>authentications on a single session this approach could produce
>misleading results.
This is on the back-channel? Yes, that's just unpredictable, there's no
guarantee that particular result would be the one.
I think I'll just pull the field, I have no use for it anyway.
-- Scott
More information about the dev
mailing list