Baron,
You can try these loggers set to trace. I think most of the protocol stuff is
handled by pac4j.
<AsyncLogger name="org.apereo" level="${sys:cas.log.level}"
includeLocation="true"/>
<AsyncLogger name="org.pac4j" level="${sys:pac4j.log.level}"
includeLocation="true"/>
<!-- DEBUG outbound and inbound headers and response-->
<AsyncLogger name="org.apache.http" level="debug" />
And spend the next 2 d crawling through the output ;)
Ray
P.S. careful with credentials in the logs
On Thu, 2022-06-16 at 07:38 -1000, Baron Fujimoto wrote:
Notice: This message was sent from outside the University of Victoria email
system. Please be cautious with links and sensitive information.
Is there a way to log or trace the actual CAS protocol messages exchanged with
a client? The logs provide a wealth of details, but not the actual protocol
messages exchanged that I've found. We haven't really used Aperero's CAS for
SAML yet, but I know the Shibboleth IdP can do this, and there are SAML trace
browser extensions as well. I'm hoping for something analogous for the CAS
protocol stuff specifically.
--
Baron Fujimoto <[email protected]<mailto:[email protected]>> ::: UH Information
Technology Services
minutas cantorum, minutas balorum, minutas carboratum descendus pantorum
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/a/apereo.org/d/msgid/cas-user/f839e1ff4266e82239beb76b1f9c11a7bc1c5503.camel%40uvic.ca.
