custom flow problems
Cantor, Scott
cantor.2 at osu.edu
Fri Jan 16 16:01:52 EST 2015
> The filenames have to be very specific to create a user flow and have it
> located. But I don't understand how you could ever get far enough to reach
> the servlet without it finding the flow, and it can't run the flow without
> setting the attemptedFlow property, unless there's a bug.
>
> I'd have to try to reproduce it or see a log trace.
FWIW, the place setAttemptedFlow is called is logged on DEBUG here in the SelectAuthenticationFlow action:
log.debug("{} Selecting inactive authentication flow {}", getLogPrefix(), descriptor.getId());
So you should have that in the log. For your servlet to be running, your flow had to have been called, and that log line has to have run for that to happen.
-- Scott
More information about the dev
mailing list