IDP 2.3.6 Stops Sending SAML 1 Responses.

[Zico]

You can use "ALL" / "TRACE" instead of "DEBUG", though your log file will
be bigger but it will help you check deep.

On Tue, May 1, 2012 at 4:40 AM, Montoya,Jose T <jtmontoya at mdanderson.org>wrote:

> This is what I have at this time:
> I'm changing the IDP logger to Trace, maybe that gives more detail.
> Any other loggers I can add?
>
> <!-- Logs IdP, but not OpenSAML, messages -->
>    <logger name="edu.internet2.middleware.shibboleth">
>        <level value="DEBUG" />
>    </logger>
>
>    <!-- Logs OpenSAML, but not IdP, messages -->
>    <logger name="org.opensaml">
>        <level value="DEBUG" />
>    </logger>
>
>    <!-- Logs LDAP related messages -->
>    <logger name="edu.vt.middleware.ldap">
>        <level value="INFO"/>
>    </logger>
>
>    <!-- Logs inbound and outbound protocols messages at DEBUG level -->
>    <logger name="PROTOCOL_MESSAGE">
>        <level value="DEBUG" />
>    </logger>
>    <logger
>
>  name="edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.ShibbolethAttributeResolver"
>    >
>        <level value="DEBUG" />
>    </logger>
>
>    <!-- Logs cookie information -->
>    <logger
> name="edu.internet2.middleware.shibboleth.idp.session.IdPSessionFilter">
>        <level valule="DEBUG" />
>    </logger>
>
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>



-- 
Best,
Zico
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20120501/c9b88f2b/attachment.html