<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
On Apr 24, 2014, at 5:06 PM, Wessel, Keith <<a href="mailto:kwessel@illinois.edu">kwessel@illinois.edu</a>> wrote:<br>
<div><br class="Apple-interchange-newline">
<blockquote type="cite"><span style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;">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.</span><br style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
</blockquote>
</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>As Scott mentioned, turn up the LDAP logging and see what pops up.</div>
<div><br>
</div>
<div>Paul</div>
<div><br>
</div>
<br>
<div apple-content-edited="true">Paul Hethmon<br>
Chief Software Architect<br>
<a href="mailto:paul.hethmon@clareitysecurity.com">paul.hethmon@clareitysecurity.com</a><br>
<br>
</div>
<br>
</body>
</html>