IDP4 (4.3.1) Context Check Intercept - Actions after the View is displayed

[Check]

Scott,

Thanks for getting back to me.  Understand about IDP4 EOL.  We'll be going
to IDP5 at some point, but that's above my pay grade.

If that view is an end-state, then I may be hosed with this approach.
That's unfortunate.  I was hoping to be able to do something like the
Consent Intercept does with the terms of use.  It does its test to see if
you have a cookie set, takes you to a form if you don't, you have to
accept the terms of use, then you click Submit and it sets the cookie.

So that one does:
Test Condition [cookie], if not set show form [terms of use], click submit,
set [cookie], continue.

Was hoping the Context Check one could do something similar:
Test Condition [attribute], if not set show form [rules], click submit, set
[AD property], continue.

Thanks for the info.




On Mon, Dec 16, 2024 at 2:21 PM Cantor, Scott <cantor.2 at osu.edu> wrote:

> > I'm pretty new with IDP4
>
> V4 has been EOL since September (not that it matters in this scenario,
> just noting it).
>
> > So basically, I've got Context Check Intercept working to the
> > point where the documentation and examples end. But once
> > the view/template/form is displayed, I need the user to be
> > able to click a button and run a script.
>
> There is nothing more the IdP allows after that point is reached, the
> event the interceptor signals terminates the converrsation and the flow has
> ended (the view in question is an "end-state", that is, a view rendered as
> the last step of a webflow).
>
> Anything else the view offers is outside the scope of the IdP (short of a
> URL routing somebody back into the IdP at some other endpoint, which would
> start a new flow conversation).
>
> I don't have any ability to go through the rest, that's far outside the
> bounds of free support.
>
> The closest tool provided for what you're asing about would be the
> External interceptor since that can run arbitrary Java/JSP code (and link
> out to anything else), and would optionally result in the conversation
> ending depending on what it signaled back.
>
> -- Scott
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20241216/da3b6c95/attachment.htm>