Context navigation in the Abstract Profile Actions.

[Rod Widdowson]

> I was talking about the authentication method. 

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.

It seems we do have a question to answer whether it is break to break
someone's configuration at run time by just removing the AuthN method
function from the language, or break it at run time by providing different
information.

I had favoured the latter until I realized this weekend that a user will
always have the option to use scripting to achieve something.  So although a
user may be blocked temporarily, they will have an option to allow them to
proceed,

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.

/Rod