Attribute resolver warning on start-up

[Wessel, Keith]

Well... hoping Scott hasn't spent any time looking at the local federation metadata I sent him. That turns out to not be the file at fault. And my apologies to the AAF folks, as well.

Turns out my commenting that out was a false positive because (1) I had other comments in those sections which turned into nested comments which (2) resulted in errors in the log that I overlooked and in my metadata providers not being loaded.

After removing those nested comments and commenting out metadataproviders one at a time, the problem, I hesitate to say, is the InCommon metadata. I'm pulling in the production aggregate. 

Furthermore, Scott was correct. There is a single SP in InCommon who has requested unscoped values for scoped affiliation.

I'll take this one to InCommon operations. But, I think it's safe to say that this isn't something I did, and it's not in any way inhibiting operations of the IDP or, presumably, processing of the InCommon metadata.

Thanks, all.

Keith


-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Rod Widdowson
Sent: Friday, July 03, 2015 1:58 AM
To: 'Shib Users'
Subject: RE: Attribute resolver warning on start-up

> I thought it was the same one I've seen when there are
> values like "member" inside a scoped affiliation attribute. 

That's what the intent of that warning is...

> I'm
> sure Rod will chime in to correct me tomorrow.

I share everyone's bafflement...  I'll try to reproduce.

Rod

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