Dependency in Attribute def

[David Bantz]

Thanks Scott.   As often, it seems clear enough once you explain it!

To be explicit, deleting 
 <resolver:Dependency ref="UASystemID" />
as referring to a non-existing attribute definition, while
retaining the expression of LDAP attribute dependency by
 sourceAttributeID="UASystemID” 
removed the parse error and generated the desired result.

David Bantz
UAlaska IAM

On Fri, 29 Aug 2014, at 11:41 , Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 8/29/14, 3:27 PM, "David Bantz" <dabantz at alaska.edu> wrote:
>> 
>> UASystemID is used successfully in other attribute definitions, like:
>>   <resolver:AttributeDefinition
>> id="uaUsername"xsi:type="Simple"xmlns="urn:mace:shibboleth:2.0:resolver:ad
>> "
>>           sourceAttributeID="UASystemID">
>>      <resolver:Dependency
>> ref="myLDAP" /> ...
> 
> You're using it in the Dependency element, not just as a
> sourceAttributeID. The constraint violated is referring to the Dependency
> ref value, not the sourceAttributeID.
> 
> It's just catching the mistake before it happens at runtime, you specified
> a dependency on a connector or attrbute definition called UASystemUD that
> doesn't exist. That's probably a field from a data connector but not the
> name of one.
> 
> -- Scott
> 
> -- 
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20140829/045b6645/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://shibboleth.net/pipermail/users/attachments/20140829/045b6645/attachment-0001.bin