Building a custom consent & password expiration plugin for Shib3

[Cantor, Scott]

> 2) We don't have the TOU and password expiration data in LDAP, only in an
> Oracle database, so we need custom SQL calls to check/update

The attribute resolver doesn't care where its data comes from so that's not an issue, but the rest of your requirements would be incompatible with the existing examples certainly.

> Unfortunately, I cannot influence this requirement in any way, even to
> accommodate what the technology can do, but I still need to make it happen
> in a very tight timeline.

Unless you're a very good Java programmer with Spring and WebFlow experience and the ability to quickly digest others' code, you should probably look for professional help. Just being honest. "It must happen" doesn't change reality, and there's no magic documentation forthcoming from me, not with everything else on my plate.

-- Scott