debugging expiring password intercept

[Paul B. Henson]

On Fri, Jun 02, 2017 at 01:21:01PM +0000, Cantor, Scott wrote:

> My guess is the cookie is already set to prevent nagging but there's
> no way to tell. You'd have to run it under a debugger or manually add
> logging to the flow definition file.

No, I cleared all of the idp-test.cpp.edu cookies from my browser each
time before testing, so I don't think that's the case.

> Aside from trying to see what it's doing with webflow logs, which are
> pretty hard to follow, adding something like this to various
> <action-state> elements would usually provide a hint.
> 
>         <on-entry>
>             <evaluate expression="T(org.slf4j.LoggerFactory).getLogger('mycategory').debug('Running some action')" />
>         </on-entry>

Ah, ok; so I found expiring-password-flow.xml which looks like it does
the magic. Can you put this on-entry debugging stuff inside a
decision-state stanza as well as an action-state stanza? Looks like the
first thing it does is a decision-state that checks the attribute then
either goes to an action-state or another decision-state depending on the
return value. I'll stuff some debug logs in here and see if I can figure
out what's going on, thanks for the tip.

-- 
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