question regarding context check intercept

[Cantor, Scott]

> Sounds like I need a Context Check Intercept and a velocity view to display
> the tasks. This would work fine in the case where a deadline has passed (no
> "continue" option).  However, I do not think that a CCI can resume the
> current authentication if the user selects "continue".  What data would the
> view POST and to what URL?

Its entire design is based on triggering an error event. It doesn't display anything unless that event happens and then it's up to the error layer. It's impossible to resume anything once that happens or there would be a bug (though I still maintain a suspicion that trying to prevent the IdP from issuing assertions is something that I wouldn't personally count on being absolutely bulletproof in the face of a determined user).

> Can I somehow use the terms-of-use flow?

Very awkward at best I would think.

>  Or do I need to write my own
> custom flow for this?  If a custom flow, can I use XML and scripts to avoid
> writing java code?

Depends on what the flow had to do, at some point it becomes silly to avoid doing in Java something that is much more work to do other ways. We have scripted action support so it's possible to script just about anything but that's not meant to be used for extensive work. But I doubt there's any code involved here. The LDAP part is just resolving an attribute and the flow itself is pretty much checking the attribute and then either entering a view-state or just doing nothing.

> We are running IDP 3.3.2.  Maybe this will be easier in 3.4 ?

Not in any way I can think of really.

-- Scott