<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div><br></div><div>On Dec 15, 2015, at 11:26 AM, Vignesh, Vanna G. <<a href="mailto:vignesh@musc.edu">vignesh@musc.edu</a>> wrote:<br><br></div><blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">2015-12-15 09:00:22,785 - ERROR [net.shibboleth.idp.profile.impl.ResolveAttributes:240] - Profile Action ResolveAttributes: Error resolving attributes: Invalid Attribute resolver configuration<o:p></o:p></p>
<p class="MsoNormal">2015-12-15 09:00:22,937 - ERROR [net.shibboleth.idp.consent.flow.ar.impl.AbstractAttributeReleaseAction:150] - Profile Action PopulateAttributeReleaseContext: Unable to locate attribute context<o:p></o:p></p>
<p class="MsoNormal">Even with the debug level of IDP and LDAP logs, this is what I see. It looks like attribute-resolver is not initiated.</p></div></blockquote><br><div>I don't have the bug at hand regarding attribute consent, but the underlying issue is an invalid attribute-resolver.xml configuration.</div></body></html>