IdPv3 CAS Debugging

[Marvin Addison]

On Mon, Mar 14, 2016 at 5:01 PM Lucia Siochi <Lucia.Siochi at cpcc.edu> wrote:

> I am setting up the built-in CAS service in IdPv3 and need to see what the
> CAS response is that’s being sent back to the CAS client.
>
> I tried setting idp.loglevel.messages  to DEBUG in conf/logback.xml:
>
>     <variable name="idp.loglevel.messages" value="DEBUG" />
>
> but I didn’t notice any difference in the output.
>
Sorry, that won't work for CAS protocol messages since they're not handled
by the SAML machinery but instead by Velocity. I've needed to do this
myself on a few occasions, but worked around it by turning up logging on
the client. If that's not an option, I have a couple suggestions:

1. Servlet filter to log HTTP response, e.g.
http://logback.qos.ch/recipes/captureHttp.html
2. Log output of velocity template

I've used both approaches in other projects quite successfully. 1 is
probably easier to configure, but broader in scope (which may or may not be
preferable). Here's a gist for approach #2:

https://gist.github.com/serac/211c65de13eec4914cf0

Feel free to file a RFE issue for this if you'd like. I think I could work
in approach #2 to apply just to CAS protocol views now that I think about
it. Ideally the same logger that dumps SAML protocol messages would include
CAS protocol messages as well.

M
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160315/d8b7600f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 2555 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/users/attachments/20160315/d8b7600f/attachment-0001.jpg>