Strange problem with the MCB and attribute resolving
kwessel at illinois.edu
Fri Apr 25 10:49:46 EDT 2014
Just when I think I have this logging figured out, I go and ask a pretty silly question. I shoulda figured this one out. Thanks, Paul and Scott, I'm sure this will do the trick.
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Paul Hethmon
Sent: Thursday, April 24, 2014 4:19 PM
To: Shibboleth Users
Subject: Re: Strange problem with the MCB and attribute resolving
On Apr 24, 2014, at 5:06 PM, Wessel, Keith <kwessel at illinois.edu<mailto:kwessel at illinois.edu>> wrote:
I tried turning up the MCB log level to debug and saw no more details about the specific error from the LDAP search failure. I can't reproduce the error using the IDP's attribute resolver with aacli.
MCB just piggybacks onto the Shib resolver instance. So the only logging it has would be about getting that instance. There are some statements at DEBUG level when it gets data. A WARN if it can't get resolver instance. If it got the resolver instance, but no actual data (which sounds like that is happening here), then it would end up logging nothing.
As Scott mentioned, turn up the LDAP logging and see what pops up.
Chief Software Architect
paul.hethmon at clareitysecurity.com<mailto:paul.hethmon at clareitysecurity.com>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users