debugging expiring password intercept
Paul B. Henson
henson at cpp.edu
Sat Jun 3 19:59:14 EDT 2017
On Fri, Jun 02, 2017 at 10:03:43PM -0400, Brent Putman wrote:
> Well, it doesn't run automatically. You have to explicitly enable it
> on the profile config. So you'd need something like this on the
> relevant profile config (here for SAML 2 SSO):
Aw, crap. Put my dunce cap on for the day, as I certainly didn't do
that.
> https://wiki.shibboleth.net/confluence/display/IDP30/ProfileInterceptConfiguration
I'm sure I reviewed this documentation when I first installed idp 3, but
it hadn't seemed to changed much for 3.3, so I didn't really focus much
on it during the upgrade. Looking more closely, I now see that it
mentions Expiring Password as a new interceptor flow.
> https://wiki.shibboleth.net/confluence/display/IDP30/ExpiringPasswordInterceptConfiguration
This is the page I was mostly referring to while trying to get it
working, and I guess I never quite connected the dots to having to go
explicitly modify relying-party.xml to enable it, d'oh 8-/.
Thanks much for leading the horse to water, hopefully I can sort out how
to drink on my own from here :).
--
Paul B. Henson | (909) 979-6361 | http://www.cpp.edu/~henson/
Operating Systems and Network Analyst | henson at cpp.edu
California State Polytechnic University | Pomona CA 91768
More information about the users
mailing list