SHIB3: Building a custom consent & password expiration workflow

[dqluan]

Hi everyone,

I didn't realize that "consent" mean something else. I just want to do a
custom Password Expiry / Terms of Use agreement.

Thanks!

Quang Luan

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

> Hi everyone,
>
> This is my first time here. I posted the same question to the development
> list, so please forgive the spam and ignore this message if you have seen
> it.
>
> Have anyone had to build a custom workflow for ToU agreement and password
> expiration in SHIB3 because of exotic organizational requirements? If so,
> how did you do it? I am brand new to SHIB3, so any suggestion is
> appreciated.
>
> My requirements:
>
> 1) Custom business logic: The organization wants passwords not to expire
> automatically after a date, but rather after that date, the user will have
> 3 more logins, each time they will be reminded, before the password
> actually expires.
>
> 2) We cannot modify the Shib3 code itself.
>
>
> From what I understand, this kind of "soft expiration" logic is not
> supported out of the box.
>
> Thanks again! And have a great day.
> Quang Luan
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170518/f17c89dd/attachment.html>