Building a custom consent & password expiration plugin for Shib3

[dqluan]

Hi again,

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.

So if I...

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

2) Base on the general structure of the existing two interceptor jar files,
create two new flows with custom logic in the Post-Auth interception point
(follow the naming rule "intercept/flowID", inherit from
"intercept.abstract", and list the flow ID in the profile-intercept.xml
config file

3) Enable the new interceptors in relying-party.xml

4) Restart the Idp service

Does this sound somewhat sensible?

Thanks,

Quang Luan


On Thu, May 18, 2017 at 10:32 AM, dqluan <dqluan at gmail.com> wrote:

> Thanks again Scott. Those suggestions are really appreciated and I will
> start digging into the code.
>
> I wasn't expecting magic, just pointers :-)
>
> Have a great day!
>
> Quang Luan
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20170519/ff383916/attachment.html>