IDPv3 Attribute Resolver help

[Peter Schober]

* Tim Williams <tmw at autotrain.org> [2016-11-08 13:07]:
> On 07/11/16 14:09, Peter Schober wrote:
> > Logging is key here, and data not being sent is another, later step.
> > The logs (on DEBUG) will tell you exactly what attributes have been
> > resolved, with how many values, and whether or why not they will be
> > released.
> 
> Hmm, I originally had DEBUG logging turned on and I was advised in an
> earlier reply on this list to turn it off because it was too noisy and
> didn't provide much useful information for non-developers.

Yes, I meant (but didn't say so) to enable DEBUG logging (only) for the
parts you're interested in. Try adding this to your conf/logback.xml:

  <logger name="net.shibboleth.idp.attribute.resolver" level="DEBUG"/>

and either reload the logging config via

  /opt/shibboleth-idp/bin/reload-service.sh -id shibboleth.LoggingService

or wait for 5 min for it to become active
(idp.service.logging.checkInterval in conf/services.properties).

Once you're happy with the resolver you could change that logger to
(s/resolver/filter/):

  <logger name="net.shibboleth.idp.attribute.filter" level="DEBUG"/>

if you're having trouble getting the attribute released.
Or just remove it again.
-peter