Attribute resolver warning on start-up

[Wessel, Keith]

Yeah, that's not adding up for me, Scott. Only occurrence of the string AttributeValue (checked with case-insensitive grep) in my metadata in the InCommon metadata, and that's entity tags. My local federation metadata, which appears to be the problem as the warning goes away when I comment out its provider, is what's generating the warning, and I see no attribute values in there.

Any other thoughts from anyone?

Any AAF folks on the list who can chime in since that's the software that's generating this metadata file?

Keith


-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Thursday, July 02, 2015 4:26 PM
To: Shib Users
Subject: Re: Attribute resolver warning on start-up

On 7/2/15, 4:47 PM, "users on behalf of Wessel, Keith" <users-bounces at shibboleth.net on behalf of kwessel at illinois.edu> wrote:

>Alright, forgive my confusion. Values? As in values for the attribute?

Yes, an <AttributeValue> element.

> I didn't know those could be in metadata; only in an assertion sent by an IDP. Am I looking for attributeValue tags in my metadata?

Inside a RequestedAttribute, yes.

>And since that's so similar to the earlier line I sent, I don't think that's my trouble maker, either.

If there are no values in there, then I don't know what's causing the warning. Maybe I misread it. I thought it was the same one I've seen when there are values like "member" inside a scoped affiliation attribute. I'll re-read it or I'm sure Rod will chime in to correct me tomorrow.

-- Scott

-- 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net