IdPv3 CAS Protocol Update

[Cantor, Scott]

On 4/2/13 10:57 AM, "Marvin Addison" <marvin.addison at gmail.com> wrote:

>> There
>> would be an action that would extract information from the request that
>> needs to be accessible later on, probably some kind of
>> AuthenticationRequirementsContext.
>
>Sounds straightforward, but I didn't see an existing component like that.

Well, the component doing the extracting of information would be yours,
that's a CAS issue. The context, if it were a shared context type that
wasn't SAML specific or CAS specific would be a common component, but I
don't think it exists yet, no.

>> One of the things we talked about in Columbus was the idea of whether to
>> try and collapse common pieces across protocols into one context type
>> (like basic message metadata such as issuer, timestamp, etc.) or leave
>> them protocol-specific.
>
>I like this idea, but I would imagine defining anything more than
>"who, what, when" might be challenging. In any case it would make
>building protocol-specific contexts easier.

I know, but historically we have not found this to work all that well in
practice and were leaning toward just duplicating contexts that carried
information specific to a protocol even if they were similar. But I don't
think we know how to solve the follow on problem of common actions that
are protocol unaware, but need access to protocol information.

This gets more into Brent's design areas than mine, but I was just trying
to answer the initial question. I know that the intent is for actions to
communicate to other actions or subflows using context subtypes.

-- Scott