Flows/Actions: What level of Granularity?

[Rod Widdowson]

Now that Scott has put together the framework I want start coding up the
PrincipalConnectors

I've not done any of these before so I'm looking for guidance on how many
actions/what granularity to make an action.

Consider the CryptoPrincipal.  We need to

1) Get the Id from the NameID (or NameIdentifier)
2) Decode it
3) Parse it
4) Check the NameQualifier
5) Check the SPNameQualifier
6) Check the responderId
7) Set the principal

So is this best set up one action, or seven, or some number in between.  I
strikes me that (1) needs to be separate (so we can easily build the SAML1
and SAML2 flows) and off the top of my head I'd put (2,3) and (4,5,6)
together and again leave (7) separate.  That way (1, 4-5-6, 7) can be shared
amongst all flows.  I guess we can put 4,5,6 and 7 together as well.

But others have more experience of putting these flows together and will
provide guidance.  I'll note that I am explicitly not thinking about the
legacy flow right now.  I'd like to get this the way it should be and then
do violence to the code to make the legacy flow work.

A supplementary question is whether it would be usual to have a distinct
subcontext to carry information between these actions?

Rod