idp-access.log in v3 IdP?
Cantor, Scott
cantor.2 at osu.edu
Thu Oct 29 09:41:28 EDT 2015
On 10/29/15, 7:38 AM, "users on behalf of Alex Stuart" <users-bounces at shibboleth.net on behalf of alex.stuart at ed.ac.uk> wrote:
>Sure, but we often have difficulty getting our users to find the correct
>part of an idp-process.log, never mind correlate that with a web access
>log.
The access log wasn't correlated with the rest of the logs either, at least that I know of. IP address is certainly the simplest correlation tool in most cases.
> Log messages like:
>
>2015-10-29 11:11:41,076 - DEBUG
>[org.opensaml.saml.saml2.binding.decoding.impl.HTTPRedirectDeflateDecoder:64]
>- Decoded RelayState: cookie:1446117095_9058
>
>or
>
>2015-10-29 11:27:58,903 - DEBUG
>[net.shibboleth.idp.saml.profile.impl.BaseIdPInitiatedSSORequestMessageDecoder:68]
>- Beginning to decode message from HttpServletRequest
>
>just seem an inauspicious way to announce the start of user interaction.
That's really a different issue in my mind. If there's something more needed on DEBUG, I can add that.
-- Scott
More information about the users
mailing list