Attribute does not resolve and

[Benjamin Cherian]

Whoops! All good now. I changed the IDs, and saw the same log messages on
restart, so I assumed the issue persisted. Changing Ids resolved the issue
I had initially. Thanks!

On 2/4/15, 11:44 AM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:

>> I changed the definition so that the Attribute Definition ID is
>>different
>> than the static attribute ID which is different than the SAML2 name.
>>Still
>> seeing the same logs for the new ID where it is setting
>>sourceAttributeID
>> to three different items. This is the new definition:
>
>Yea, you've found a bug.
>(https://issues.shibboleth.net/jira/browse/IDP-589)
>
>Apologies for that , it will be fixed in the next release.
>
>Meantime going back to you initial question:
>
>>2015-02-04 10:23:53,841 - INFO
>[net.shibboleth.idp.attribute.resolver.spring.BaseResolverPluginParser:58]
> -
>Parsing configuration for AttributeDefinition plugin with id : cquser
>> 2015-02-04 10:23:53,842 - DEBUG
>[net.shibboleth.idp.attribute.resolver.spring.ad.BaseAttributeDefinitionPa
>rs
>er:95] - Attribute Definition 'cquser': setting sourceAttributeId cquser
>
>You need to identify the 'cquser' in the DEBUG line (and the same for data
>connectors).
>Instead if you want to look at the attribute being defined look at the
>INFO
>line above it (which I assume you edited out in your initial post).
>
>Given that, what is the issue you are experiencing?
>
>Rod
>
>
>
>-- 
>To unsubscribe from this list send an email to
>users-unsubscribe at shibboleth.net