SHIB3: Building a custom consent & password expiration workflow
dqluan at gmail.com
Thu May 18 13:30:14 EDT 2017
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
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
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
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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users