Attribute resolver warning on start-up
Wessel, Keith
kwessel at illinois.edu
Thu Jul 2 21:51:38 EDT 2015
Link sent off-list. Quite puzzled here.
Keith
-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Thursday, July 02, 2015 5:04 PM
To: Shib Users
Subject: Re: Attribute resolver warning on start-up
On 7/2/15, 5:50 PM, "users on behalf of Wessel, Keith" <users-bounces at shibboleth.net on behalf of kwessel at illinois.edu> wrote:
>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.
Well, I checked the code and the warning is emitted when there's an Attribute being mapped into internal form and it has values on the input side. Then it sees if the output set of values is empty and logs that. So I don't see how it's possible to trigger without an input SAML attribute sitting somewhere that has values inside it.
If it's suppressing the warning when you remove a particular metadata source, can you link to a copy?
-- Scott
--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
More information about the users
mailing list