Building a custom consent & password expiration plugin for Shib3

[Cantor, Scott]

On 5/19/17, 5:43 AM, "dev on behalf of dqluan" <dev-bounces at shibboleth.net on behalf of dqluan at gmail.com> wrote:

> After reading the documentation, I believe that the two built-in Interceptor flows "Terms of Use Consent" and "Expiring
> Password 3.3" in the Post-Auth interception point are essentially official versions of what I am trying to achieve.

They're examples with significant usability, yes.

>1) Disable these two flows, not editing them in anyway, just editing the relying-party.xml config file to disable them, then

There's nothing to disable, neither is on by default.

> Does this sound somewhat sensible?

Yes, provided you touch and place nothing in system/ you're essentially on the right track, but that sort of elides the details of "do all the work" in step 2 there.

-- Scott