Working 3.1.1 IDP upgrade to 3.2.0 now broken

[Roderick Grau]

Thank you Scott and Rod.  I was focused on the data connector and did not look anywhere else.

Adding a sourceAttributeID to the resolver:AttributeDefinition for OPEID fixed the issue.

Not having a sourceAttributeID was a working config prior to 3.2.0.

Do you still want a bug filed?

-Rod
> On Dec 3, 2015, at 12:30 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> 
> On 12/3/15, 12:22 PM, "users on behalf of Rod Widdowson" <users-bounces at shibboleth.net on behalf of rdw at steadingsoftware.com> wrote:
> 
> 
> 
>>> OPEID is a static data connector.
>> 
>>> 2015-12-03 10:25:30,448 - WARN
>> [net.shibboleth.idp.attribute.resolver.spring.ad.BaseAttributeDefinitionPars
>> er:100] - Attribute Definition 'OPEID': sourceAttributeID was not specified
>> but is required
>> 
>> From the look of that warning, it's also an Attribute Definition?  I cannot
>> see how that warning could be spat out from the DataConnector you quoted.  
> 
> Yes, the warning was added in 3.2 for IDP-665, but the underlying issue with the config being wrong was always there. If it was "working" before, it was working in some accidental fashion. We must have also added a constraint to one of the definitions, though, which should have been surfaced as a checked exception.
> 
> -- Scott
> 
> -- 
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net

--
Roderick Grau
Enterprise Infrastructure Services
University at Albany
1400 Washington Avenue Ext.
Albany, New York 12222