Authentication Subsystem

[Cantor, Scott]

On 8/16/13 2:13 PM, "Marvin S. Addison" <marvin.addison at gmail.com> wrote:

>Ok, that makes sense. The InitializeAuthenticationContext action led me
>to believe that the pattern is for a flow to initialize the context it
>needs (recall seeing that pattern elsewhere), but I can imagine based on
>your examples that it's probably not the common case.

No, and it may be that the action there now moves to the profile packages,
unless it's sufficiently generic to be reused, but I also don't know if I
would keep the name the same, understanding that it "belongs" in some
sense to the profile flows, not to the authentication subsystem/subflow.

Right now, it's mainly a bootstrap for testing so that I can create a
working flow without needing any profile handling.

Your point is also well-taken in that right now that action is where I
would have the Spring layer loading in the AuthenticationFlowDescriptor
collection. Since we don't want that to be duplicated across profiles,
either the action itself might change or perhaps we just rely on
configuring the collection of flows as a shared bean. Not sure yet.

> In any case I can
>pretty clearly imagine how the CAS protocol acting at the profile layer
>will hand off the the authentication subsystem, which is good.

Yes, the details won't involve significant changes later, just gluing the
flows together appropriately.

-- Scott