Context navigation in the Abstract Profile Actions.

[Cantor, Scott]

On 1/6/14, 3:55 AM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:
>
>I'd missed that, apologies.  You've seen that I've cobbled something
>together (using the FlowId), but that was just something I had to hand and
>as you said OOB it isn't compatible with V2 in any way.

No. The method value in V2 is an actual SAML authentication constant,
which is in itself broken for all sorts of reasons (e.g. SAML 1 uses
different values from SAML 2, but we only allowed for one or the other).

I completely changed all that, and the only code now that knows for sure
what will end up in the assertion is going to be inside the SAML profile
flow. The rest of the system deals with multiple custom Principal objects
representing all sorts of different possible values until the profile
narrows it down to the one to send back. So the resolver or filter can't
rely on a single value anymore.

Unless it's the internal value, the flow ID, which is what you used.

>I suppose that as a third option we could leave the code in place but use
>a
>different XML type.  Thus users will be alerted, but will have an
>alternative to hand without having to resort of scripting, but perhaps I'm
>overthinking the problem.

I think if we were going to provide something, that's how to do it. Call
it something else (probably AuthenticationFlow) and then it doesn't get
confused as the other.

-- Scott