Action event IDs for missing child contexts ?

[Cantor, Scott]

On 2/5/14, 12:03 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:

>Okay. So as a general rule, choose the closest/narrowest event id.

Yeah, and I guess stick to "subsystems" as the level of granularity, so I
defined them for Authentication and C14N, but I wouldn't get into the
child contexts much.

The vast, vast majority of current events are pretty meaningless except
for authentication/c14n-related flow management. I think we'll have more
useful ones in the SAML flows as we finish them up, to signal different
runtime error conditions.

e.g. failure to validate/locate a response endpoint (the one that people
know so well today, no peer endpoint available)

-- Scott