picketlink-handlers and handleStatusResponseType

[bkrisler]

Hi,

I am trying to create a handler that sits on the response chain. I thought it would be as simple

as adding my handler to the list of handlers in picketlink-handlers.xml, and then having my

custom handler extend BaseSAML2Handler, overriding handleStatusResponseType.

I then setup a simple ServiceProvider and IdentityProvider to see if my custom handler works.

I get a log message that my handleRequestType is called (indicating my code is loading correctly),

however my override of handleStatusResponseType never gets called.

Am I going about this wrong?

Also, the docs indicate that the ordering of picketlink-handlers is important, but I can

find no documentation on what the order implies? Are they processed from first to last?

Thanks

Brian

[anil.saldhana]

All the handlers defined in the handlers.xml will be invoked in the order of declaration. Try to use the debugger to see if it is invoking your handler.

[bkrisler]

I see what was happening, I placed my listener on the IDP, thinking that the handleStatusResponseType would get called when the response left the IDP, but prior to getting to the SP.  By adding my listener to the SP, I see that I am indeed getting invoked.

Is it possible to add a filter on all outgoing messages, for message inspection?

Thanks

Brian

[anil.saldhana]

At the SP, if you enable the trace logging on "org.picketlink", you should see trace information.

On the IDP side, there is the IDPSamlDebugValve that you can put in your context.xml to get some information on saml payload.