Question on Logging

[Cantor, Scott]

On 11/13/15, 10:26 AM, "users on behalf of Brewer, Lee" <users-bounces at shibboleth.net on behalf of lee.brewer at Vanderbilt.Edu> wrote:



>Then I can see the SAML response which contains the attributes and values.
>As noted.. there is nothing here about common.attribute and LDAP.

There's nothing remotely resembling a V2 log trace there at all, actually. There are a ton of things that would be logged unless they're turned off.

You're also creating a ton of noise by logging the opensaml category.

The first log line of the attribute resolution during SSO is:

10:50:03.067 - 128.146.94.198 - DEBUG [edu.internet2.middleware.shibboleth.idp.profile.saml2.AbstractSAML2ProfileHandler:478] - Resolving attributes for principal 'cantor.2' for SAML request from relying party 'https://carmenwiki.osu.edu/shibboleth'


(Just ran a test in dev here to see what it was.)

The attribute stuff is mostly in edu.internet2.middleware.shibboleth.common.attribute: e.g.

10:50:03.067 - 128.146.94.198 - DEBUG [edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.ShibbolethAttributeResolver:119] - shibboleth.AttributeResolver resolving attributes for principal cantor.2
10:50:03.067 - 128.146.94.198 - DEBUG [edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.ShibbolethAttributeResolver:275] - Specific attributes for principal cantor.2 were not requested, resolving all attributes.
10:50:03.067 - 128.146.94.198 - DEBUG [edu.internet2.middleware.shibboleth.common.attribute.resolver.provider.ShibbolethAttributeResolver:314] - Resolving attribute eduPersonPrincipalName for principal cantor.2


So I guess you have a broken logging config, basically.

-- Scott