IdPv3 CAS Protocol Update

[Marvin Addison]

> 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.

> 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'm not sure keeping them separate works in this particular case.

Probably too early to say, in part because some expected integration
points aren't implemented yet. That's not to say you shouldn't try to
factor out common protocol data into a base context for other
potential gains.

M