IdP3.2.1 Increase Logging for flow execution

[Cantor, Scott]

On 9/9/16, 9:24 AM, "users on behalf of O'Dowd, Josh" <users-bounces at shibboleth.net on behalf of Josh.O'Dowd at mso.umt.edu> wrote:

> It has been suggested that if there is a FlowExecutionListener wired in, to increase
> logging from that, for long requests, to include flow id, state id, and transition event.

I doubt you're going to learn much that simply turning up IdP logging itself wouldn't tell you about where the requests get hung up. Either way the volume probably wouldn't work well in production.

>  I noticed that there is a bean wired in the IdP webflow-config
> called profileRequestContextFlowExecutionListener.  I am wondering if we can use that
> listener to add some logging directives when the error occurs?

I would just turn up webflow logging if you really think it's going to tell you anything. I think you will end up causing hangups by increasing overhead, it's a "measuring it changes the state" sort of situation.

There aren't a lot of culprits to consider really. If you use LDAP or a remote database, it's pretty much guaranteed one of those is the problem.

-- Scott